Re: gpu-viv-mx6q and libEGL.so/libEGL.so.1

[Eric Nelson <eric.nelson@boundarydevices.com>]

Hi Philip,

On 07/26/2013 02:54 AM, Philip Craig wrote:
> On Fri, Jul 26, 2013 at 10:44 AM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi all,
>>
>> When running the sample apps in /opt/viv_samples/vdk
>> under strace on a frame-buffer only build, I can see that
>> something is trying to load libEGL.so (no trailing 1).
>>
>> Looking at the recipe, I'm not quite grokking how this is
>> placed into the image though.
>>
>> I can see a symlink being created pointing libEGL.so at
>> libEGL.so.1 here:
>>
>>
>> https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc#L130
>>
>> Somehow or another, the symlink is ending up in the -dev package
>> though:
>>
>> $ find gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/ \
>>          -name libEGL\*
>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6-dev/usr/lib/libEGL.so
>> gpu-viv-bin-mx6q/1_3.0.35-4.0.0-r5.0/packages-split/libegl-mx6/usr/lib/libEGL.so.1
>>
>> Can anybody give some guidance on where and how that's happening?
>
> See lines 152 and 153 of gpu-viv-bin-mx6q.inc. If something needs
> libEGL.so then this probably needs to be changed to how libgles and
> libgles2 are done. It would be nice to document exactly where the
> dependency is though so that we know when we can remove the hack once
> it is fixed.
>

Seeing and understanding are completely different things ;)

I'm reading this to mean that this clause translates to
libEGL.so:
	libEGL${SOLIBSDEV}

I'm also unclear on whether simply moving that clause to
FILES_libegl-mx6 is the right thing to do.

Regards,


Eric