Re: Ideas for scripts, to save work, when building several boards

[Ulf Samuelsson <ulf.samuelsson@atmel.com>]

Marcin Juszkiewicz skrev:
> Dnia piątek, 14 sierpnia 2009 o 09:44:51 Ulf Samuelsson napisał(a):
>> The reason for doing a script is to allow building multiple stuff
>> when I am sleeping or travelling, and as long as things complete
>> I do not mind the 10 minute pauses.
>>
>> When I am working interactively, I do not want to specify MACHINE
>> everytime I do something
>>
>> Maybe this is something that would work...
>> alias bitbake="MACHINE=${BB_MACHINE} /path/to/bitbake"
> 
> I do that in this style:
> 
> for mach in LIST-OF-BOARDS;do MACHINE=$mach bitbake something;done
> 
> This works fine in Bash and allow to do anything from remote etc.
> 
> My last use was:
> 
> for mach in `ls openembedded/conf/machine/at91*`;do export MACHINE=`basename 
> $mach .conf`; bitbake -cclean base-files sysvinit task-base task-boot; bitbake 
> console-image;done
> 
> To make it work you should have to use MACHINE ?= "machinename" in conf/*.conf 
> files or just not set MACHINE there at all.
> 
OK, nice to know.

It takes less than 2 minutes to rebuild the cache on my machine
so it is less of an issue for me.

My buildscript will generate logs which is nice to have,
but I could do this with this method as well,

Also, my main goal is not to get a machine running for any
specific purpose.
I want to make sure that a certain machine will complete its
build properly, and if I do what people propose, won't I
sometimes miss a problem, because I previously built a machine
which worked OK, and then I use the result of that build instead
of the result for this specific machine.

Example:
If you build a recipe which has
SRC_URI_append_at91sam9263ek for the sam9263ek
and then bitbake MACHINE=at91sam9g45ek,
will that force a rebuild of the recipe?

If you then build at91sam9263ek again,then
does it do this again.
If not, then I have to do it my way.

> Regards, 


-- 
Best Regards
Ulf Samuelsson