All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: gpu-viv-mx6q and libEGL.so/libEGL.so.1
Date: Thu, 25 Jul 2013 17:44:16 -0700	[thread overview]
Message-ID: <51F1C660.3000401@boundarydevices.com> (raw)

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?

Does anybody know where the missing reference to libEGL.so
might be coming from? This doesn't appear to be a hard-coded
linker dependency from any of the sample apps or from the
other shared libraries.

Please advise,


Eric


             reply	other threads:[~2013-07-26  0:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  0:44 Eric Nelson [this message]
2013-07-26  9:54 ` gpu-viv-mx6q and libEGL.so/libEGL.so.1 Philip Craig
2013-07-26 10:05   ` Philip Craig
2013-07-26 13:46     ` Otavio Salvador
2013-07-26 14:10     ` Eric Nelson
2013-07-26 14:06   ` Eric Nelson
2013-07-26 14:15   ` Eric Nelson
2013-07-26 15:31     ` Otavio Salvador

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=51F1C660.3000401@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=meta-freescale@yoctoproject.org \
    /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.