[oe] Ideas for scripts, to save work, when building several boards
ulf.samuelsson at atmel.com
Thu Aug 13 14:10:24 CEST 2009
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-220.127.116.11
>>>> I generated a "MAKEALL" script which will
>>>> source a file "board_list.sh" with board build commands
>>>> 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
>>> 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:
Thanks for helping out, but it does not work as expected.
I first create a local.conf for the at91sam9261df
and bitbake x11-image.
Then I do "MACHINE=at91sam9g20dfc bitbake console-image".
A console-image is built,but for the at91sam9261df,
which is stored in "tmp/deploy/glibc/images/at91sam9261df"
The bitbake does not generate u-boot/kernel or at91bootstrap
for the at91sam9260dfc
I believe that most at91 chips can use the same file system,
so it makes sense to do it this way anyway.
I assume that the at91sam9261df setup is used for the console-image.
There could be a few cases where this is ineffient or simply wrong.
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
More information about the Openembedded-devel