On 11 July 2013 11:53, Andreas Oberritter <o...@opendreambox.org> wrote: >> 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.
The GLESv2 backend will work best, because the v1 backend is crippled by v1's limitations and lack of testing. And GLESv1 is already disabled explicitly in EXTRA_OECONF (that this patch should remove). I'm leaning towards rejecting this as it doesn't serve a purpose, unless someone can say that they're actually using the GLESv1 backend (that upstream admits isn't tested). Ross _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
