From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 06/17] evas.inc: Require virtual/gles2 and enable gl engine
Date: Sat, 23 Oct 2010 10:21:08 +0200 [thread overview]
Message-ID: <i9u5tk$1dm$1@dough.gmane.org> (raw)
In-Reply-To: <4cc22963.0311650a.0c4d.ffffaf60@mx.google.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23-10-10 02:15, fidencio@profusion.mobi wrote:
> From: Eduardo Lima (Etrunko) <eblima@gmail.com>
> -DEPENDS = "librsvg eina eet freetype jpeg libpng virtual/libx11 libxext libxrender fontconfig libfribidi"
> +DEPENDS = "librsvg eina eet freetype jpeg libpng virtual/gles2 virtual/libx11 libxext libxrender fontconfig libfribidi"
We have no virtual/gles2 in OE yet. The way I currently enable it is to
build a gles provider (e.g. libgles-omap3) and then build evas, it will
pick it up automatically. That sucks, but I haven't found a way that
would make it work without making all gles users machine specific :(
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMwpr0MkyGM64RGpERAmN6AJ9ZA/tg+QRmhDLOSB06SGt87eQXoACfeaa+
iyH+jBKfvBabxzvLMJdUp7U=
=BJTQ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-10-23 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 0:15 [PATCH 06/17] evas.inc: Require virtual/gles2 and enable gl engine fidencio
2010-10-23 8:21 ` Koen Kooi [this message]
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='i9u5tk$1dm$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