Two distros with same MACHINE

Two distros with same MACHINE

[Yevhen Kyriukha]

[-- Attachment #1: Type: text/plain, Size: 220 bytes --]

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?

[-- Attachment #2: Type: text/html, Size: 241 bytes --]

Re: Two distros with same MACHINE

[Nicolas Dechesne]

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..

Re: Two distros with same MACHINE

[Yevhen Kyriukha]

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

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!

[-- Attachment #2: Type: text/html, Size: 938 bytes --]

Re: Two distros with same MACHINE

[Martin Jansa]

[-- 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 --]

Re: Two distros with same MACHINE

[Mike Looijmans]

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

Re: Two distros with same MACHINE

[Koen Kooi]

Op 14 aug. 2014, om 13:13 heeft Mike Looijmans <mike.looijmans@topic.nl> het volgende geschreven:

> 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.

Multi machine builds were possible with OE classic as well. It was tricky in the beginning (2005-ish) with the giant sysroot, but after per-arch sysroots were available it was pretty safe to do multi machine builds.

regards,

Koen

> 
> 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
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core