From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Shared work directory proof of concept
Date: Mon, 18 Apr 2011 07:21:53 +0100 [thread overview]
Message-ID: <1303107713.5518.49.camel@rex> (raw)
One of the items on the 1.1 feature list is sharing work directories.
This is desirable for example for gcc where the same sources are
unpacked and patched for gcc-cross-initial, gcc-cross-intermediate,
gcc-cross, gcc-runtime and so on.
I've done a little experimentation with this and the code linked to
below shows its at least possible and the kind of changes we might need
to make to bitbake to support it:
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/gcc-sharedwork&id=4a22c2212466ef3bcb20960b1f99f8509347b24d
There are at least 4 issues I've noted in the commit which we'd need to
to look before we could start using this code, nothing impossible
though, just needs more work.
Cheers,
Richard
reply other threads:[~2011-04-18 6:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1303107713.5518.49.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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