From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [yocto] opengl / libgl / libgles
Date: Thu, 06 Sep 2012 17:10:47 +0100 [thread overview]
Message-ID: <5048CB07.9000502@r-finger.com> (raw)
In-Reply-To: <C92CD2AA-A842-454E-9C14-FCA5FC683DAB@dominion.thruhere.net>
On 06/09/12 15:50, Koen Kooi wrote:
>
> Op 6 sep. 2012, om 16:37 heeft Tomas Frydrych <tf+lists.yocto@r-finger.com> het volgende geschreven:
>
>> On 06/09/12 14:51, Burton, Ross wrote:
>>> On 6 September 2012 14:25, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>>> It's not automatic, but you can do something like this:
>>>>
>>>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?id=23b02134
>>>>
>>>> RDEPENDS_${PN} = "libGL"
>>>
>>> Ah, interesting. I'm not entirely keen on the manual dependencies but
>>> that's certainly a step in the right direction.
>>
>> Is there much that actually links against libGL / libgles? Things like
>> cogl dlopen() these these, so you have to manually specify the RDEPENDS
>> anyway. Just thinking this could be less of an issue than it might appear.
>
>
> xbmc is one
The problem is basically the mesa package, right? If the mesa package is
split so that the mesa libGL parts are provided separately from the more
generic parts, and any GL bits, mesa or otherwise, are only built as a
specific machine feature, then we will never have any GL bits in the
non-machine part of the sysroot, and will always be dealing with the
correct, and only, libGL. Packages that link directly to libGL would
also be machine specific, but if we are talking about a hand full
things, this is not a major issue. Or I am missing something?
Ross, I think it gets unnecessarily complicated if you start thinking of
it in the terms of hot-swapping libGL at runtime the way desktop distros do.
Tomas
next prev parent reply other threads:[~2012-09-06 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 10:00 opengl / libgl / libgles Andrei Gherzan
2012-09-06 10:19 ` Tomas Frydrych
2012-09-06 13:04 ` [yocto] " Burton, Ross
2012-09-06 13:04 ` Burton, Ross
2012-09-06 13:25 ` [yocto] " Koen Kooi
2012-09-06 13:51 ` Burton, Ross
2012-09-06 14:37 ` Tomas Frydrych
2012-09-06 14:50 ` Koen Kooi
2012-09-06 16:10 ` Tomas Frydrych [this message]
2012-09-06 16:36 ` Koen Kooi
2012-09-06 14:50 ` Burton, Ross
2012-09-06 15:55 ` Richard Purdie
2012-09-19 11:14 ` Andrei Gherzan
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=5048CB07.9000502@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=openembedded-core@lists.openembedded.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.