From: Phil Blundell <philb@gnu.org>
To: openembedded-core@lists.openembedded.org
Subject: What is TOOLCHAIN_NEED_CONFIGSITE_CACHE for?
Date: Mon, 29 Oct 2012 13:33:46 +0000 [thread overview]
Message-ID: <1351517628.13864.4.camel@phil-desktop> (raw)
This morning I happened to notice that some/all of my images had a
dependency on ncurses for no obviously good reason. (Following an
earlier small crusade these are now the only remaining dependencies on
ncurses in my build, so I would quite like to get rid of them.)
It turns out that the dependency in question is due to the code in
toolchain-scripts.bbclass (which is inherited from
populate_sdk_base.bbclass, from image.bbclass) which does:
TOOLCHAIN_NEED_CONFIGSITE_CACHE = "${TCLIBC} ncurses"
[...]
python __anonymous () {
deps = ""
for dep in (d.getVar('TOOLCHAIN_NEED_CONFIGSITE_CACHE', True) or "").split():
deps += " %s:do_populate_sysroot" % dep
d.appendVarFlag('do_configure', 'depends', deps)
}
The code in question was added in:
commit 9e87f1347788beed181476dc4563085db14a4729
Author: Lianhao Lu <lianhao.lu@intel.com>
Date: Tue Aug 16 11:15:36 2011 +0800
toolchain-script.bbclass: Collected cached site config in runtime.
[YOCTO #892]
Modify the function toolchain_create_sdk_siteconfig to collect the
cached site config files which are specified by
TOOLCHAIN_NEED_CONFIGSITE_CACHE in runtime.
Also added task dependency to ensure the cached site config files are
generated.
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
... but I don't entirely understand from that commentary what exactly is
special about ncurses that means it needs to be handled this way. Can
anybody clarify?
thanks
p.
next reply other threads:[~2012-10-29 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 13:33 Phil Blundell [this message]
2012-10-29 15:43 ` What is TOOLCHAIN_NEED_CONFIGSITE_CACHE for? Richard Purdie
2012-10-29 17:33 ` Chris Larson
2012-10-29 17:42 ` Mark Hatle
2012-10-29 17:45 ` Richard Purdie
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=1351517628.13864.4.camel@phil-desktop \
--to=philb@gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox