From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: how to share just the host tools among different builds?
Date: Mon, 5 Jan 2015 08:51:02 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1501050850080.12284@localhost> (raw)
In-Reply-To: <1420465310.25779.29.camel@linuxfoundation.org>
On Mon, 5 Jan 2015, Richard Purdie wrote:
> On Mon, 2015-01-05 at 07:53 -0500, Robert P. J. Day wrote:
> > i'm drawing a blank at the moment so this might be a trivial
> > question -- is there a way to share the non-toolchain, host tools
> > across different builds on my development host?
> >
> > if i'm doing closely-related builds (or even for totally different
> > architectures), i can see the host tools that are built under
> > tmp/sysroots/x86_64-linux/... and one would think that, theoretically,
> > those tools are appropriate for all sorts of independent builds, even
> > if the toolchain is different.
> >
> > is there a simple setting that allows me to take advantage of all
> > those host tools that were built during an initial build, and continue
> > to use them in subsequent builds?
>
> Its called sstate ;-).
>
> Just share the native parts between the builds. They're usually in a
> distro specific directory.
i suspected it was sstate-related, just wanted to be sure i could be
that specific. will go back to reading now ...
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2015-01-05 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 12:53 how to share just the host tools among different builds? Robert P. J. Day
2015-01-05 13:41 ` Richard Purdie
2015-01-05 13:51 ` Robert P. J. Day [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=alpine.LFD.2.11.1501050850080.12284@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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