From: Andreas Oberritter <obi@opendreambox.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] cogl-1.0: add option to enable GLES1
Date: Thu, 11 Jul 2013 12:53:44 +0200 [thread overview]
Message-ID: <51DE8EB8.60908@opendreambox.org> (raw)
In-Reply-To: <CAJTo0Laa7if2poYd_8AeLYDq8obefuw5F7ygSi+uz4LYpWrOkg@mail.gmail.com>
On 11.07.2013 10:52, Burton, Ross wrote:
> On 11 July 2013 01:56, Andreas Oberritter <obi@opendreambox.org> wrote:
>> Only PACKAGECONFIG options for GL and GLES2 were available before.
>
> The rationale behind this was that the GLES1 support isn't tested,
> mainly as there's not a lot of hardware that can't also do GLESv2.
> Was this enabled for completeness or are you actually restricted to
> GLESv1?
It's for completeness, so if you have libraries for both GLES1 and
GLES2, you can compare them easily and then choose the one that works
better for your application. If nothing else, then this may improve test
coverage. Because it's disabled by default, introducing this option
doesn't have any bad side effects. On the good side, it explicitly
disables GLES1, so if a later version of cogl switches to
auto-detection, the behaviour of the build won't change.
Regards,
Andreas
next prev parent reply other threads:[~2013-07-11 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 0:56 [PATCH 1/3] cogl-1.0: put each library into its own package Andreas Oberritter
2013-07-11 0:56 ` [PATCH 2/3] cogl-1.0: make building cogl-pango optional Andreas Oberritter
2013-07-11 8:56 ` Burton, Ross
2013-07-11 9:18 ` Tomas Frydrych
2013-07-11 10:59 ` Andreas Oberritter
2013-07-11 0:56 ` [PATCH 3/3] cogl-1.0: add option to enable GLES1 Andreas Oberritter
2013-07-11 8:52 ` Burton, Ross
2013-07-11 10:53 ` Andreas Oberritter [this message]
2013-07-11 11:01 ` Burton, Ross
2013-07-11 11:51 ` Phil Blundell
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=51DE8EB8.60908@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.