Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Crosstool-NG unnecessary rebuilds [BUG]
Date: Fri, 15 Mar 2013 09:25:25 +0100	[thread overview]
Message-ID: <20130315092525.0fd38998@skate> (raw)
In-Reply-To: <EE5E77B503DE9A478B63A89AAD2585EDB66A63@vpane.excalyptech.com>

Dear Przemyslaw Wrzos,

On Fri, 15 Mar 2013 11:18:44 +1100, Przemyslaw Wrzos wrote:

> So just a question about the effect of that. If we remove that
> dependency then won't this be inconsistent with how the internal
> buildroot toolchain build works?

Nothing in Buildroot tries to get rebuilt automatically when there are
configuration changes. This has been the Buildroot policy for a long
time, and only the Crosstool-NG backend was moving away from this
general policy.

If you make a change in the Buildroot configuration, it's up to you to
understand the consequences of the change, and take the appropriate
actions (a complete "make clean all" in some situations, remove some
stuff in other situations, etc.).

> Or does it not matter because the
> internal toolchain is going to be deprecated eventually anyway.

From the discussions of the last Buildroot Developers Meeting, it is
really not clear whether the internal toolchain backend will be
deprecated one day. There are still some integration problems in the
Crosstool-NG backend (download infrastructure, license infrastructure)
that are not easy to handle.

See http://elinux.org/Buildroot:DeveloperDaysFOSDEM2013 (search for
"Switching to ct-ng as the default toolchain backend has been in the
plans for several years").

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-03-15  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13  3:14 [Buildroot] Crosstool-NG unnecessary rebuilds [BUG] Przemyslaw Wrzos
2013-03-13  7:37 ` Thomas Petazzoni
2013-03-13  8:12   ` Przemyslaw Wrzos
2013-03-13 18:10   ` Yann E. MORIN
2013-03-14  7:48     ` Thomas Petazzoni
2013-03-14 18:21       ` Yann E. MORIN
2013-03-15  0:18       ` Przemyslaw Wrzos
2013-03-15  8:25         ` Thomas Petazzoni [this message]
2013-03-18  2:38           ` Przemyslaw Wrzos

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=20130315092525.0fd38998@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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