From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Samuel Stirtzel <s.stirtzel@googlemail.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [meta-kde][PATCH] qt4-x11-free 4.8.0 bbappend: fix GLES configure switch and turn it on for AM335x SoCs as well
Date: Tue, 24 Apr 2012 15:21:44 +0100 [thread overview]
Message-ID: <11414981.06zDBIpEfK@helios> (raw)
In-Reply-To: <CAGiJk9d5oeXCULH2c4xh47yLpa6TRB6upVYzz233+z+6fdrNog@mail.gmail.com>
On Tuesday 24 April 2012 15:54:17 Samuel Stirtzel wrote:
> For this .bbappend it is no problem, over time the machine specific
> stuff will disappear (it is only there for testing).
>
> But I see a problem with kde-workspace [1].
> If it should build kwin_gles then it depends on libgles, but not every
> machine has libgles.
> It would be no problem if virtual/libgl is used but that don't work
> for machines that use virtual/egl.
>
> Or is there a way to build time recommend something instead of depending on
> it?
You can add an RRECOMMENDS, however if the library is already dynamically
linked to some other library then there will be a hard dependency on that
library which via the shlibdeps code in package.bbclass will become an
RDEPENDS; nothing in our system can really work around that if it's integrated
into a single binary (or indivisible group of binaries).
It seems to me that either the functionality needs to be split out into its
own separate package which can be pulled in optionally (if possible), or more
likely in this case the recipe needs to become machine-specific and be
dependent on some item in MACHINE_FEATURES.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-04-24 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 14:25 [meta-kde][PATCH] qt4-x11-free 4.8.0 bbappend: fix GLES configure switch and turn it on for AM335x SoCs as well Koen Kooi
2012-04-23 15:28 ` Samuel Stirtzel
2012-04-23 15:46 ` Paul Eggleton
2012-04-23 19:39 ` Koen Kooi
2012-04-23 21:16 ` Paul Eggleton
2012-04-24 13:54 ` Samuel Stirtzel
2012-04-24 14:21 ` Paul Eggleton [this message]
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=11414981.06zDBIpEfK@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=s.stirtzel@googlemail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox