Building for multiple machines

Building for multiple machines

[Elvis Dowson]

Hi,
        What should I do build for multiple machines ? 

I have an overo-oe repository, but I need to temporarily build u-boot for a different board. 

In my auto.conf, the entry is MACHINE="overo"

u-boot board definitions for say beagleboard, have named the board "beagle" 

So, would an appropriate command be 

bitbake u-boot-omap3 MACHINE="beagle"


Elvis Dowson

Re: Building for multiple machines

[Frans Meulenbroeks]

2010/10/11 Elvis Dowson <elvis.dowson@mac.com>:
> Hi,
>        What should I do build for multiple machines ?
>
> I have an overo-oe repository, but I need to temporarily build u-boot for a different board.
>
> In my auto.conf, the entry is MACHINE="overo"
>
> u-boot board definitions for say beagleboard, have named the board "beagle"
>
> So, would an appropriate command be
>
> bitbake u-boot-omap3 MACHINE="beagle"
>
>
> Elvis Dowson

I guess trying this would ahve been much faster than waiting for an answer here.

And OE does not have an auto.conf

Frans

Re: Building for multiple machines

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-10-10 08:27, Frans Meulenbroeks wrote:
> 2010/10/11 Elvis Dowson <elvis.dowson@mac.com>:
>> Hi,
>>        What should I do build for multiple machines ?
>>
>> I have an overo-oe repository, but I need to temporarily build u-boot for a different board.
>>
>> In my auto.conf, the entry is MACHINE="overo"
>>
>> u-boot board definitions for say beagleboard, have named the board "beagle"
>>
>> So, would an appropriate command be
>>
>> bitbake u-boot-omap3 MACHINE="beagle"
>>
>>
>> Elvis Dowson
> 
> I guess trying this would ahve been much faster than waiting for an answer here.
> 
> And OE does not have an auto.conf

OE *does* have an auto.conf, pretty much since the start:

koen@dominion:/OE/org.openembedded.dev/conf$ git blame bitbake.conf |
grep auto.conf
00f6a165 (Chris Larson 2004-12-09 01:08:40 +0000 695) include conf/auto.conf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMssEUMkyGM64RGpERAqxMAJ9ORcv5iii/70qi6c7EC7ReXlKSQgCgm4UF
qgXeKzlpaIRCTrylt4wM+hU=
=eNId
-----END PGP SIGNATURE-----

Re: Building for multiple machines

[Elvis Dowson]

On Oct 11, 2010, at 11:47 AM, Koen Kooi wrote:
>> 
>> I guess trying this would ahve been much faster than waiting for an answer here.
>> 
>> And OE does not have an auto.conf
> 
> OE *does* have an auto.conf, pretty much since the start:

There was a reason why I didn't try it right away. A while back, i had a working overo-oe, and auto.conf was set to MACHINE="overo"

After that, I changed it to MACHINE="beagleboard". 

It created two output folders in tmp/deply for both the targets, but the images didn't work properly, I had some issues. Can't recall exactly what it was. So, I had to delete my tmp folder, and repeat the build process afresh, this time, with only MACHINE='beagleboard".

I was wondering what the recommended process is for building for multiple machine architectures?

Elvis Dowson

Re: Building for multiple machines

[Frans Meulenbroeks]

2010/10/11 Koen Kooi <k.kooi@student.utwente.nl>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11-10-10 08:27, Frans Meulenbroeks wrote:
>> 2010/10/11 Elvis Dowson <elvis.dowson@mac.com>:
>>> Hi,
>>>        What should I do build for multiple machines ?
>>>
>>> I have an overo-oe repository, but I need to temporarily build u-boot for a different board.
>>>
>>> In my auto.conf, the entry is MACHINE="overo"
>>>
>>> u-boot board definitions for say beagleboard, have named the board "beagle"
>>>
>>> So, would an appropriate command be
>>>
>>> bitbake u-boot-omap3 MACHINE="beagle"
>>>
>>>
>>> Elvis Dowson
>>
>> I guess trying this would ahve been much faster than waiting for an answer here.
>>
>> And OE does not have an auto.conf
>
> OE *does* have an auto.conf, pretty much since the start:
>
> koen@dominion:/OE/org.openembedded.dev/conf$ git blame bitbake.conf |
> grep auto.conf
> 00f6a165 (Chris Larson 2004-12-09 01:08:40 +0000 695) include conf/auto.conf

Yeah, that line is there. What I wanted to say is that if you pull
from git there is no auto.conf file

frans@frans-desktop:~/workspace/openembedded.git$ find | grep auto.conf
frans@frans-desktop:~/workspace/openembedded.git$

So I still feel we do not have an auto.conf (but the user can provide
an auto.conf if (s)he wishes)

Frans

PS: I normally set MACHINE in either the environment (as a bash env
var) or in local.conf

Re: Building for multiple machines

[Frans Meulenbroeks]

2010/10/11 Elvis Dowson <elvis.dowson@mac.com>:
>
> On Oct 11, 2010, at 11:47 AM, Koen Kooi wrote:
>>>
>>> I guess trying this would ahve been much faster than waiting for an answer here.
>>>
>>> And OE does not have an auto.conf
>>
>> OE *does* have an auto.conf, pretty much since the start:
>
> There was a reason why I didn't try it right away. A while back, i had a working overo-oe, and auto.conf was set to MACHINE="overo"
>
> After that, I changed it to MACHINE="beagleboard".
>
> It created two output folders in tmp/deply for both the targets, but the images didn't work properly, I had some issues. Can't recall exactly what it was. So, I had to delete my tmp folder, and repeat the build process afresh, this time, with only MACHINE='beagleboard".
>
> I was wondering what the recommended process is for building for multiple machine architectures?
>
> Elvis Dowson

I've build multiple machines in one tmp but often they are for
different architectures (e.g. hawkboard and beagleboard (whcih is
armv5 and armv7a resp)
If you are going to mix distro's things might become more troublesome
(and machine specific pinnings (with DEFAULT_PREFERENCE) might also
cause mismatches).

Of course you can also change your TMPDIR (and set it e.g. to
tmp_${DISTRO}_${MACHINE})
That way you'll get different tmp dirs (probably you want to inherit
rm_work to keep the space usage manageable).

Have fun! Frans

Frans