From: David Corvoysier <david.corvoysier@orange.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libgles: postpone the check for a missing GLES provider
Date: Wed, 11 Dec 2013 15:05:03 +0100 [thread overview]
Message-ID: <52A8710F.7040406@orange.com> (raw)
In-Reply-To: <52A862B4.50103@orange.com>
Sorry, I did another try from a clean environment and the second
solution didn't work either: LIBGLES_DEPENDENCIES has the right
(modified) value when it the LIBGLES_CONFIGURE_CMDS is evaluated, but
not when the dependencies themselves are evaluated (I think it happens
in pkg-generic.mk).
So, the build doesn't fail on the LIBGLES_CONFIGURE_CMDS test, but if
the xx_userland package has not been installed beforehand, it is not
installed automatically when libgles is built.
David
Le 11/12/2013 14:03, David Corvoysier a ?crit :
> Guys,
>
> The first solution did not work (as yann pointed out, the variable is
> not exported), but the second does.
> Who's in for a patch (me ?)
>
> David
>
next prev parent reply other threads:[~2013-12-11 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 15:18 [Buildroot] [BR2_EXTERNAL] Ability to specify regular packages behaviour from external.mk David Corvoysier
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 [this message]
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=52A8710F.7040406@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox