From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Error due GTK+3 new rdepends on libgl
Date: Wed, 14 Oct 2015 09:54:13 -0300 [thread overview]
Message-ID: <CAP9ODKofedBS83=fKmPk_GyfV09UTUPRDxcCPgy7dAtozjsSUg@mail.gmail.com> (raw)
In-Reply-To: <CAHiDW_G10f50vzvQGWvnCc=2ztB0QLLTNrxDMLB-K9p6Wd=KUw@mail.gmail.com>
On Wed, Oct 14, 2015 at 4:31 AM, Jussi Kukkonen
<jussi.kukkonen@intel.com> wrote:
> On 14 October 2015 at 00:42, Burton, Ross <ross.burton@intel.com> wrote:
>>
>>
>> On 13 October 2015 at 22:32, Otavio Salvador
>> <otavio.salvador@ossystems.com.br> wrote:
>>>
>>> This includes a forced rdepends on libgl and I see no reason for this.
>>
>>
>> Mainly because gtk3-demo will link to libGL.so on startup.
>>
>> It would be interesting to see what happens on platforms where libgl.so
>> isn't available if you remove the dependency. If GTK+ handles that
>> gracefully then we can make the rdepends conditional on DISTRO_FEATURES.
>
>
> If dlopening libGL.so.1 fails, gtk3-demo will not run. I'm sure it's
> possible to patch it to fail gracefully (after all GL is only needed for one
> demo out of many) and I would guess upstream would take that as well, but
> for now I just did the minimum required to get the current dependencies
> correct in the recipe.
In worse case, it would be a RRECOMMENDS. Anyway fixing it seems the
best way to handle this IMO.
--
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
next prev parent reply other threads:[~2015-10-14 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 21:32 Error due GTK+3 new rdepends on libgl Otavio Salvador
2015-10-13 21:42 ` Burton, Ross
2015-10-13 21:44 ` Otavio Salvador
2015-10-13 21:45 ` Burton, Ross
2015-10-14 7:31 ` Jussi Kukkonen
2015-10-14 12:54 ` Otavio Salvador [this message]
2015-10-14 17:44 ` 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='CAP9ODKofedBS83=fKmPk_GyfV09UTUPRDxcCPgy7dAtozjsSUg@mail.gmail.com' \
--to=otavio.salvador@ossystems.com.br \
--cc=jussi.kukkonen@intel.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.