[oe] Ideas for scripts, to save work, when building several boards
Koen Kooi
k.kooi at student.utwente.nl
Thu Aug 13 12:46:19 UTC 2009
On 13-08-09 14:18, Ulf Samuelsson wrote:
> Koen Kooi skrev:
>> On 13-08-09 12:07, Ulf Samuelsson wrote:
>>> Koen Kooi skrev:
>>>> On 13-08-09 09:13, Ulf Samuelsson wrote:
>>>>> Since I will need to test multiple boards,
>>>>> I decided to write some scripts which I will
>>>>> check in later today in origin/ulf/linux-2.6.30.2
>>>>>
>>>>> I generated a "MAKEALL" script which will
>>>>> source a file "board_list.sh" with board build commands
>>>>>
>>>>> <SOF>
>>>>> build_board sam9263dfc x11-gpe-image
>>>>> build_board sam9g45ek opie-image
>>>>> build_board sam9g10df x11-gpe-image
>>>>> build_board sam9g20dfc console-image
>>>>> build_board sam9260dfc console-image
>>>>> build_board sam9261df x11-image
>>>>> build_board sam9xedfc console-image
>>>>> <EOF>
>>>>
>>>> You do know that you can do that with MACHINE=foo bitbake bar, right?
>>>>
>>>
>>> Didn't try that.
>>> I assume this means that the cross compiler is not rebuilt,
>>
>> Unless you poked at the gcc recipes, no, it won't get rebuilt.
>>
>>> Is the root fs assembled from ipks then?
>>
>> if you use rootfs_ipk.bbclass, yes.
>>
>> Note that the official angstrom buildguide has mentioned that for years:
>> http://www.angstrom-distribution.org/building-angstrom
>>
>
> I guess I can create a separate
> "build/conf/<machine>.conf" per machine and link
> "build/conf/local.conf" to this file.
>
> if "MACHINE=<machine> bitbake<whatever>" does not work
It does the exact same thing here, except that the angstrom method skips
the 10 minute reparse and only parses things that got changed in between.
This is how the angstrom autobuilder works and it hasn't shown any
problems in the method, it only highlighted broken zrecipes (e.g.
zaurus-updater).
regards,
Koen
More information about the Openembedded-devel
mailing list