Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] fix bitbake ERRORS for machine not having virtual/egl
Date: Thu, 09 Sep 2010 20:28:50 +0200	[thread overview]
Message-ID: <i6b912$snb$1@dough.gmane.org> (raw)
In-Reply-To: <4C88FA2F.1030206@eukrea.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09-09-10 17:15, Eric Bénard wrote:
> Hi Koen,
> 
> Le 09/09/2010 17:10, Koen Kooi a écrit :
> On 09-09-10 14:11, Eric Bénard wrote:
>>> * This patch creates a egl.inc which contains the compatible machines
>>> for
>>> recipes depending on virtual/egl and thus will workaround this error.
>>
>> The intent is good, but I have to NAK this for the time being.
>>
>> Could you change that to use:
>>
>> COMPATIBLE_MACHINE = "omap3"?
>>
> in egl.inc ?
> Should this also be changed in powervr-drivers/libgles-omap.inc ?
> 
> Then, how do you handle omap3 machines which don't have GLES engine (ex
> OMAP3503) ?

That's handled by the initscript:
http://gitorious.org/angstrom/openembedded/blobs/org.openembedded.dev/recipes/powervr-drivers/libgles-omap3/rc.pvr#line33

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMiSdiMkyGM64RGpERAgZ9AKCc8SaPq3w9pL5ZC/vMFgo9mdv05ACgn7CM
rBtN/3iHVSWLrI5nUy3Grm4=
=1czF
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-09-09 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 12:11 [PATCH] fix bitbake ERRORS for machine not having virtual/egl Eric Bénard
2010-09-09 12:19 ` Frans Meulenbroeks
2010-09-09 15:10 ` Koen Kooi
2010-09-09 15:15   ` Eric Bénard
2010-09-09 18:28     ` Koen Kooi [this message]
2010-09-09 19:04       ` Eric Bénard
2010-09-09 19:34   ` [PATCH v2] " Eric Bénard

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='i6b912$snb$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    /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