Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] asking for advice on improving our buildroot setup
Date: Thu, 07 Jul 2011 13:42:10 +0200	[thread overview]
Message-ID: <87aacqs4fh.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1310033360.2076.18.camel@sven> (Sven Neumann's message of "Thu,  07 Jul 2011 12:09:20 +0200")

>>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:

Hi,

 Sven> As you can imagine this build consumes a lot of time and disk space.
 Sven> Currently I can think of two ways to improve this:

 Sven> (1) Add an initial step that builds a toolchain and then use that
 Sven>     toolchain from the following steps. This would save the time
 Sven>     to rebuild the toolchain for each of the steps.

I think that is the best/easiest option.

 Sven> (2) Combine all steps and build different rootfs from within the
 Sven>     same buildroot tree. I read that this would be supported. But
 Sven>     I would like to get advice from you first. Is there a chance
 Sven>     that this will work for the described setup?

Unfortunately not, buildroot only knows of a single rootfs - So you'll
need to build the 2 rootfs'es seperately.

The only other option I could think of is perhaps to combine the two
rootfs'es and include the factory test sw in the device rootfs if that's
an option?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-07-07 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 10:09 [Buildroot] asking for advice on improving our buildroot setup Sven Neumann
2011-07-07 11:42 ` Peter Korsgaard [this message]
2011-07-07 11:59 ` Thomas Petazzoni
2011-07-07 12:22   ` Daniel Mack
  -- strict thread matches above, loose matches on Subject: below --
2011-07-21  7:53 Arnout Vandecappelle

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=87aacqs4fh.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