All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Two distros with same MACHINE
Date: Thu, 14 Aug 2014 13:13:55 +0200	[thread overview]
Message-ID: <53EC99F3.1070004@topic.nl> (raw)
In-Reply-To: <20140813112531.GU14848@jama>

On 08/13/2014 01:25 PM, Martin Jansa wrote:
> 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.
>

I'd name it as one of the major improvements over classic OE, being able to 
build multiple machines while sharing common things.

As for disk space, I found that it helps to occasionally remove the tmp dir 
and start over. That usually yields a few GB back. It would be nice if rm_work 
tried harder to remove stuff.

M.



Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Bezoek ons op 9 en 10 september tijdens Technology for Health Den Bosch (stand 53)
http://www.technologyforhealth.nl



  reply	other threads:[~2014-08-14 11:13 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
2014-08-14 11:13         ` Mike Looijmans [this message]
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=53EC99F3.1070004@topic.nl \
    --to=mike.looijmans@topic.nl \
    --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.