From: David Corvoysier <david.corvoysier@orange.com>
To: buildroot@busybox.net
Subject: [Buildroot] [BR2_EXTERNAL] Ability to specify regular packages behaviour from external.mk
Date: Tue, 10 Dec 2013 16:18:08 +0100 [thread overview]
Message-ID: <52A730B0.3020104@orange.com> (raw)
Hi,
I have been testing BR2_EXTERNAL to generate a firmware for a target
that provides proprietary egl and gles implementations.
I have created a custom userland package for my target that "provides"
egl and gles, but I still need to specify a dependency towards it in
libegl and libgles.
Before BR2_EXTERNAL, I used to patch buildroot's
package/opengl/libgles.mk and package/opengl/libegl.mk directly:
ifeq ($(BR2_PACKAGE_XX_USERLAND),y)
LIBGLES_DEPENDENCIES += xx-userland
endif
Now, I would like to add these lines to my external.mk, but I fail on a
LIBXX_CONFIGURE_CMDS that exits on error if LIBGLES_DEPENDENCIES are empty.
The thing is that since external.mk is included after all other
makefiles, my modifications to LIBXX_DEPENDENCIES are applied only after
the creation of the LIBXX_CONFIGURE_CMDS, thus causing the exit on error.
I managed to overcome this issue by moving the inclusion of external.mk
before all other makefiles, but I have no idea if this is the right way
to go: what do you think ?
David Corvoysier
next reply other threads:[~2013-12-10 15:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 15:18 David Corvoysier [this message]
2013-12-10 19:07 ` [Buildroot] [PATH 0/1] Fix GLES when a provider is defined in BR2_EXTERNAL Yann E. MORIN
2013-12-10 19:07 ` [Buildroot] [PATCH] package/libgles: postpone the check for a missing GLES provider Yann E. MORIN
2013-12-11 10:46 ` Arnout Vandecappelle
2013-12-11 12:25 ` Yann E. MORIN
2013-12-11 13:03 ` David Corvoysier
2013-12-11 14:05 ` David Corvoysier
2013-12-12 22:00 ` Arnout Vandecappelle
2013-12-12 22:13 ` Thomas Petazzoni
2013-12-12 23:08 ` Arnout Vandecappelle
2013-12-17 6:11 ` Thomas Petazzoni
2013-12-17 7:58 ` Yann E. MORIN
2013-12-17 9:04 ` Thomas Petazzoni
2013-12-17 22:07 ` Yann E. MORIN
2013-12-17 22:20 ` Arnout Vandecappelle
2013-12-17 22:35 ` Yann E. MORIN
2013-12-19 16:58 ` Arnout Vandecappelle
2013-12-19 20:43 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A730B0.3020104@orange.com \
--to=david.corvoysier@orange.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.