automated build of cross toolchains

Hi,

I am a newbie to buildroot, and I would like to know if it is possible to make the configuration process of buildroot automated.
I mean that, for example, if I wanted to build, in a batch mode, several cross toolchains for some specific architecturse that I would have defined beforehand, how should I proceed.
In fact, I thought about making a script that runs many times the "make config" command and that supplies the adequate configuration, but I don't think this is the best solution.
Is there any other solution like generating a default config by running "make config" and somehow modifying the .config file each time it is necessary in the script ?

If anyone got a solution, thanks for replying.

Hichem.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: boussettahichem.vcf
Type: text/x-vcard
Size: 295 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090311/ce4b2a8c/attachment.vcf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3278 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090311/ce4b2a8c/attachment.bin>

Hichem> Hi,
Hichem> I am a newbie to buildroot, and I would like to know if it is possible Hichem> to make the configuration process of buildroot automated. Hichem> I mean that, for example, if I wanted to build, in a batch mode, Hichem> several cross toolchains for some specific architecturse that I would Hichem> have defined beforehand, how should I proceed.
Hichem> In fact, I thought about making a script that runs many times the Hichem> "make config" command and that supplies the adequate configuration, Hichem> but I don't think this is the best solution.
Hichem> Is there any other solution like generating a default config by Hichem> running "make config" and somehow modifying the .config file each time Hichem> it is necessary in the script ?

Just copy your .config's somewhere else and copy them in place whenever you want to build that configuration. This is pretty much what the make <project>_defconfig make target does.

Also have a look at the make O=</path/to/build/in> support.

E.G. something like:

for project in projectA projectB projectC;
do
cp configs/$project .config
yes ''|make oldconfig
make O=/tmp/build/$project
done

(the yes '' part is to accept the defaults for new configuration options)

Bye, Peter Korsgaard