[meta-efl] question about OpenGL ES and Evas

[meta-efl] question about OpenGL ES and Evas

[Nicolas Aguirre]

Hi,

I'm building an image based on meta-efl.
I added recipes to build OpenGL ES for my hardware (allwinner sunxi
based processor with mali gpu) but i'm facing a problem.
When Evas is build, it will try to find gles includes in sysroot. If
they are found, it's correctly built with this support. So i need to
build and install all this stuff before building evas.
Which is not always the case, when i build an image from scratch for example

I would like to know wihch is the best practice in this case ?

- Add a bbappend to evas in my specific case ?
- Modify evas recipe upstream : detect opengl in distro feature and
add a dependency on virtual/gl in this case ?
- Another solution ?

Best regards,
-- 
Nicolas Aguirre
Mail: aguirre.nicolas@gmail.com
Web: http://enna.geexbox.org
Blog: http://dev.enlightenment.fr/~captainigloo/

Re: [meta-efl] question about OpenGL ES and Evas

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

On Thu, Sep 26, 2013 at 06:26:29PM +0200, Nicolas Aguirre wrote:
> Hi,
> 
> I'm building an image based on meta-efl.
> I added recipes to build OpenGL ES for my hardware (allwinner sunxi
> based processor with mali gpu) but i'm facing a problem.
> When Evas is build, it will try to find gles includes in sysroot. If
> they are found, it's correctly built with this support. So i need to
> build and install all this stuff before building evas.
> Which is not always the case, when i build an image from scratch for example
> 
> I would like to know wihch is the best practice in this case ?
> 
> - Add a bbappend to evas in my specific case ?
> - Modify evas recipe upstream : detect opengl in distro feature and
> add a dependency on virtual/gl in this case ?
> - Another solution ?

Combination of above :)

1) it has to be either explicitly enabled or disable, it shouldn't
autodetect it from sysroot (it doesn't detect mesa, otherwise my scripts
would find it already).

2) best way would be PACKAGECONFIG in upstream recipe and default value
can be set from DISTRO_FEATURES

3) people who don't want to enable ES (e.g. with only mesa sw available)
will be able to disable PACKAGECONFIG for that with simple .bbpappend
even when they have opengl in DISTRO_FEATURES

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]