On Tue, Apr 29, 2014 at 3:39 AM, Carlos Rafael Giani <d...@pseudoterminal.org> wrote: > By default, Chromium will try to use GLX and regular OpenGL. On embedded > platforms, these are often not present, or unaccelerated, and using EGL > and OpenGL ES instead makes more sense. To produce builds that use EGL and > OpenGL ES by default instead, this PACKAGECONFIG option can be used. > > An EGL/OpenGLES-enabled build produces a chromium version that renders > 2D and WebGL with GPU acceleration (if present). > > Signed-off-by: Carlos Rafael Giani <d...@pseudoterminal.org> > --- > recipes-browser/chromium/chromium_35.0.1883.0.bb | 8 +++++++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/recipes-browser/chromium/chromium_35.0.1883.0.bb > b/recipes-browser/chromium/chromium_35.0.1883.0.bb > index 1923b4e..1fb050f 100644 > --- a/recipes-browser/chromium/chromium_35.0.1883.0.bb > +++ b/recipes-browser/chromium/chromium_35.0.1883.0.bb > @@ -23,6 +23,10 @@ COMPATIBLE_MACHINE_armv7a = "(.*)" > > inherit gettext > > +# this makes sure the dependencies for the EGL mode are present; otherwise, > the configure scripts > +# automatically and silently fall back to GLX > +PACKAGECONFIG[use-egl] = ",,virtual/egl virtual/libgles2"
There is any way to 'force' build to use egl here and fail if something here is missing? -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
