From: Ivan Sergio Borgonovo <mail@webthatworks.it>
To: openembedded-devel@lists.openembedded.org
Subject: meta-toolchain-qt5, qttools-plugins and -nomake examples
Date: Thu, 22 Oct 2015 14:11:44 +0200 [thread overview]
Message-ID: <5628D280.10902@webthatworks.it> (raw)
I think I've been able to find all and only the packages that should be
conditionally added to RDEPENDS in packagegroup-qt5-toolchain-target.bb
from opengl.
I finally discovered why there was a problem with meta-toolchain-qt5 and
qttools-plugins... qttools-plugins doesn't get build when
-nomake examples
Now I don't understand:
- why nobody noticed this problem that doesn't seem related to opengl or
x11. Was it hidden by something else that I should take care when trying
to fix it? No one is actually baking meta-toolchain-qt5?...
- what should be considered a correct solution:
* simply remove the package that doesn't really seem that useful in a
toolchain (they should be example plugins for qtcreator)
* conditionally add it just if qt get build with examples [1]
* still adding qttools-plugins in local.conf will trigger the problem.
Is there a way to automatically enable a "package feature" if a package
get included?
One of the way to "fix" this could be to
PACKAGECONFIG_DISTRO_append_pn-qtbase = " examples..."
What is the consensus so I could adapt my patch to
packagegroup-qt5-toolchain-target.bb
and get a chance to see it merged?
thanks
[1] How? I know how to check if a DISTRO_FEATURES has been enabled but
how can I check if a package option has been enabled?
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
next reply other threads:[~2015-10-22 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 12:11 Ivan Sergio Borgonovo [this message]
2015-10-22 12:28 ` meta-toolchain-qt5, qttools-plugins and -nomake examples Anders Darander
2015-10-22 12:35 ` Ivan Sergio Borgonovo
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=5628D280.10902@webthatworks.it \
--to=mail@webthatworks.it \
--cc=openembedded-devel@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.