Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] automated build of cross toolchains
Date: Wed, 11 Mar 2009 21:52:24 +0100	[thread overview]
Message-ID: <878wnb93zr.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <49B783C6.8070107@yahoo.fr> (Hichem Boussetta's message of "Wed\, 11 Mar 2009 10\:26\:30 +0100")

>>>>> "Hichem" == Hichem Boussetta <boussettahichem@yahoo.fr> writes:

 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

      reply	other threads:[~2009-03-11 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11  9:26 [Buildroot] automated build of cross toolchains Hichem Boussetta
2009-03-11 20:52 ` Peter Korsgaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878wnb93zr.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox