Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: What is TOOLCHAIN_NEED_CONFIGSITE_CACHE for?
Date: Mon, 29 Oct 2012 12:42:56 -0500	[thread overview]
Message-ID: <508EC020.80808@windriver.com> (raw)
In-Reply-To: <CABcZANmzfXiXA5rdNQpqo33wXyFPz518dCkLe0x7rZGjOZ=Ucw@mail.gmail.com>

On 10/29/12 12:33 PM, Chris Larson wrote:
> On Mon, Oct 29, 2012 at 8:43 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Mon, 2012-10-29 at 13:33 +0000, Phil Blundell wrote:
>>> 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?
>>
>> We ship the "site" cache files with the toolchain. We decided to include
>> the generated cache files as well as the static ones. We currently
>> generate "site" files for libc and ncurses.
>>
>> You can almost certainly just set:
>>
>> TOOLCHAIN_NEED_CONFIGSITE_CACHE = "${TCLIBC}"
>>
>> and be happy since this just lists which generated cache site files to
>> include.
>
> Shouldn't it be pulled in via depends from the populate_sdk bits,
> rather than a task that's used both for image builds and toolchain
> builds, though?
>

Ya, this seems like a design issue.  The site cache files require the package to 
be built, but I was under the impression they were included with the dev items 
within that package.  If this isn't how it works, maybe this is a change we 
should consider.

--Mark



  reply	other threads:[~2012-10-29 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 13:33 What is TOOLCHAIN_NEED_CONFIGSITE_CACHE for? Phil Blundell
2012-10-29 15:43 ` Richard Purdie
2012-10-29 17:33   ` Chris Larson
2012-10-29 17:42     ` Mark Hatle [this message]
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=508EC020.80808@windriver.com \
    --to=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox