Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Reduce time for a make, possible?
Date: Thu, 18 Feb 2010 09:37:11 +0100	[thread overview]
Message-ID: <87zl370wjs.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100215194451.0aee0f65@surf> (Thomas Petazzoni's message of "Mon, 15 Feb 2010 19:44:51 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Hello,
 Thomas> On Mon, 15 Feb 2010 15:29:48 +0100
 Thomas> Tony Mozi <spooflinux@hotmail.fr> wrote:

 >> When we make a change in the buildroot like add or remove an option,
 >> it's necessary to do 'make clean' then a 'make'. Is it possible to
 >> reduce the time of this operation which is very long?

 Thomas> For the moment, it is not possible safely. However, during the
 Thomas> last Buildroot Working Day last week, this was one of the main
 Thomas> topic that we discussed. So it's definitely not a feature that
 Thomas> will be available in the coming weeks, but pretty likely in the
 Thomas> coming months or so.

Yes. For most situations you can safely add new applications without
rebuilding everything (the problem is with libraries as other
libs/programs might want to enable support for that library). Removing
stuff is more difficult, so there you need to rebuild.

Once the external toolchain stuff is more robust and we have better
package removal/addition tracking things will get better.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2010-02-18  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 14:29 [Buildroot] Reduce time for a make, possible? Tony Mozi
2010-02-15 18:44 ` Thomas Petazzoni
2010-02-18  8:37   ` 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=87zl370wjs.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