* sstate-cache
@ 2012-11-22 14:56 Jaap de Jong
2012-11-23 13:54 ` sstate-cache Jaap de Jong
0 siblings, 1 reply; 2+ messages in thread
From: Jaap de Jong @ 2012-11-22 14:56 UTC (permalink / raw)
To: openembedded-devel@lists.openembedded.org
Hi All,
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?
Any idea?
Thanks!
Jaap
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: sstate-cache
2012-11-22 14:56 sstate-cache Jaap de Jong
@ 2012-11-23 13:54 ` Jaap de Jong
0 siblings, 0 replies; 2+ messages in thread
From: Jaap de Jong @ 2012-11-23 13:54 UTC (permalink / raw)
To: openembedded-devel@lists.openembedded.org
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-11-23 14:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-22 14:56 sstate-cache Jaap de Jong
2012-11-23 13:54 ` sstate-cache Jaap de Jong
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox