From: Jaap de Jong <jaap.dejong@nedap.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: sstate-cache
Date: Fri, 23 Nov 2012 14:54:34 +0100 [thread overview]
Message-ID: <50AF801A.7000502@nedap.com> (raw)
In-Reply-To: <50AE3D1A.90106@nedap.com>
On 11/22/2012 03:56 PM, Jaap de Jong wrote:
> I have a handful of openembedded clones on a single machine and I would
> like to use as little diskspace as possible, so I'm wondering if it is
> possible to share the directory build/sstate-cache among these different
> clones?
>
To be a bit more precise, these are the variables to work with:
SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
SSTATE_MIRRORS ?= "\
file://.* http://someserver.tld/share/sstate/ \n \
file://.* file:///some/local/dir/sstate/"
Does every clone (which might be translated at the same time) has to
have its own local SSTATE_DIR?
Or is it ok to point every clone to one single directory, like:
SSTATE_DIR ?= "${HOME}/sstate-cache"?
Or should I use SSTATE_MIRRORS for that purpose?
Thanks!
Jaap
prev parent reply other threads:[~2012-11-23 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 14:56 sstate-cache Jaap de Jong
2012-11-23 13:54 ` Jaap de Jong [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=50AF801A.7000502@nedap.com \
--to=jaap.dejong@nedap.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox