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 14:03:48 +0100 [thread overview]
Message-ID: <52A862B4.50103@orange.com> (raw)
In-Reply-To: <201312111325.49600.yann.morin.1998@free.fr>
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
Le 11/12/2013 13:25, Yann E. MORIN a ?crit :
> Arnout, All,
>
> On Wednesday 11 December 2013 11:46:59 Arnout Vandecappelle wrote:
>> On 10/12/13 20:07, Yann E. MORIN wrote:
>>> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>>>
>>> Because some GLES providers may be in BR2_EXTERNAL, $(LIBGLES_DEPENDENCIES)
>>> might be empty hwen we test it.
>>>
>>> So, we can't rely on it to define LIBGLES_CONFIGURE_CMDS, and we must
>>> postpone the check until later, ie. at runtime.
>>>
>>> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>>> ---
>>> package/opengl/libgles/libgles.mk | 13 +++++++++----
>>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/package/opengl/libgles/libgles.mk b/package/opengl/libgles/libgles.mk
>>> index ec157ac..c2e1acf 100644
>>> --- a/package/opengl/libgles/libgles.mk
>>> +++ b/package/opengl/libgles/libgles.mk
>>> @@ -22,11 +22,16 @@ ifeq ($(BR2_PACKAGE_GPU_VIV_BIN_MX6Q),y)
>>> LIBGLES_DEPENDENCIES += gpu-viv-bin-mx6q
>>> endif
>>>
>>> -ifeq ($(LIBGLES_DEPENDENCIES),)
>>> +# Because some GLES providers may be in BR2_EXTERNAL,
>>> +# $(LIBGLES_DEPENDENCIES) might be empty right here.
>>> +# So, we can't rely on it to define LIBGLES_CONFIGURE_CMDS
>>> +# right now, and we must postpone the check until later,
>>> +# ie. at runtime.
>>> define LIBGLES_CONFIGURE_CMDS
>>> - echo "No libGLES implementation selected. Configuration error."
>>> - exit 1
>>> + if [ -z "$${LIBGLES_DEPENDENCIES}" ]; then \
>> This should be "$(LIBGLES_DEPENDENCIES)", but otherwise it looks like
>> it would work.
> I was afraid using a make variable here would be expanded too early
> again, that's why I postponed its expansion into the shell command
> itself.
>
> But it does not work either, since the variable is not exported.
>
> I'm waiting for feedback from David to confirm either or both
> solutions work...
>
> Regards,
> Yann E. MORIN.
>
next prev parent reply other threads:[~2013-12-11 13:03 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 [this message]
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=52A862B4.50103@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.