From: Martin Jansa <martin.jansa@gmail.com>
To: Yevhen Kyriukha <kirgene@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Two distros with same MACHINE
Date: Wed, 13 Aug 2014 13:25:31 +0200 [thread overview]
Message-ID: <20140813112531.GU14848@jama> (raw)
In-Reply-To: <CADV-EXF_+nNXPUEY0hJ3akxNCb0HeD+tHAYAiVcq9hACCv-ExA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On Wed, Aug 13, 2014 at 02:09:36PM +0300, Yevhen Kyriukha wrote:
> 13 Авг 2014 г. 13:51 пользователь "Nicolas Dechesne" <
> nicolas.dechesne@linaro.org> написал:
> >
> > On Wed, Aug 13, 2014 at 12:46 PM, Yevhen Kyriukha <kirgene@gmail.com>
> wrote:
> > > I have 2 distro configs that use different PACKAGECONFIG settings for
> the
> > > same package. I'm building all distros for single MACHINE. Do I need to
> set
> > > different TMPDIR to build these two distros or I can use same dir?
> > >
> >
> > yes, you should. i generally recommend to use 1 build dir for each
> > combination of <machine>, <distro> and <OE version>. keep in mind that
> > TMPDIR are 'cheap', assuming you are sharing ssate-cache, downloads
> > and using rm_work..
>
> Thanks!
I don't agree with separate dirs for <machine>.
Sharing the native sysroot and huge part of deploy/ipk/<common-arch> is
very useful for lowering disk space usage.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-08-13 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADV-EXHPuDtDk8pnFfJ4QQCVQufidX+7YuuK_FdgsEXj_46t6A@mail.gmail.com>
2014-08-13 10:46 ` Two distros with same MACHINE Yevhen Kyriukha
2014-08-13 10:50 ` Nicolas Dechesne
2014-08-13 11:09 ` Yevhen Kyriukha
2014-08-13 11:25 ` Martin Jansa [this message]
2014-08-14 11:13 ` Mike Looijmans
2014-08-14 11:26 ` Koen Kooi
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=20140813112531.GU14848@jama \
--to=martin.jansa@gmail.com \
--cc=kirgene@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.