toolchain/crosstool-NG: do not depend on the top-level Buildroot's .config
PATCH 1/1 toolchain/crosstool-NG: do not depend on the top-level Buildroot's .config
Previously, the crosstool-NG backend did depend on the top-level Buildroot's .config to detect changes in the toolchain options, using a tentatively-clever heuristic, which also included the full Buildroot's version string to push down to set the components' versions strings.
In doing so, any commit in the Buildroot tree would imply a complete rebuild of the toolchain, even in the case the toolchain options did not change, thus being a large annoyance (to say the least).
As Buildroot never guaranteed that toolchain options would be detected, even less handled, and that the internal backend does neither detect nor act on toolchain options changes, and delegate that to the user, there is no point in individualising the crosstool-NG backend's behaviour.
This reasoning also applies to the depdency on the crosstool-NG's bundled .config file, too.
So, just drop the not-so-clever heuristic, and just build the toolchain once, leaving to the user the responsibility to explictly ask Buildroot to rebuild the toolchain.
---
Changes v1 -> v2:
- properly use $(CTNG_CONFIG_FILE) (Przemyslaw)
--- toolchain/toolchain-crosstool-ng/crosstool-ng.mk | 16 ++++++---------- 1 files changed, 6 insertions(+), 10 deletions(-)
toolchain/toolchain-crosstool-ng/crosstool-ng.mk +6 -10
@@ -362,32 +362,28 @@ endef $(CTNG_DIR)/.config: | host-crosstool-ng # Default configuration -# Depends on top-level .config because it has options we have to shoe-horn -# into crosstool-NG's .config # Only copy the original .config file if we don't have one already. # Check that given config file matches selected C library. # We need to call oldconfig twice in a row to ensure the options # are correctly set ( eg. if an option is new, then the initial sed # can't do anything about it ) Ideally, this should go in oldconfig # itself, but it's much easier to handle here. - -$(CTNG_DIR)/.config: $(CTNG_CONFIG_FILE) $(BUILDROOT_CONFIG) +$(CTNG_DIR)/.config: $(Q)if [ ! -f $@ ]; then \ mkdir -p "$(CTNG_DIR)"; \ - libc="$$(awk -F '"' '$$1=="CT_LIBC=" { print $$2; }' "$<")"; \ + libc="$$(awk -F '"' '$$1=="CT_LIBC=" { print $$2; }' \ + "$(CTNG_CONFIG_FILE)" \ + )"; \ if [ "$${libc}" != "$(BR2_TOOLCHAIN_CTNG_LIBC)" ]; then \ - echo "* Inconsistency in crosstool-NG config file '$<'"; \ + echo "* Inconsistency in crosstool-NG config file '$(CTNG_CONFIG_FILE)'"; \ echo "* - buildroot configured for '$(BR2_TOOLCHAIN_CTNG_LIBC)'"; \ echo "* - given config file for '$${libc}'"; \ exit 1; \ fi; \ - cp -f $< $@; \ + cp -f $(CTNG_CONFIG_FILE) $@; \ fi - $(Q)cp -a $@ [email protected] $(call ctng-oldconfig,$@) $(call ctng-oldconfig,$@) - $(call ctng-check-config-changed,$@,[email protected]) - $(Q)rm -f [email protected] # Manual configuration ctng-menuconfig: $(CTNG_DIR)/.config
Signature · 1 line
1.7.2.5
PATCH 1/1 toolchain/crosstool-NG: do not depend on the top-level Buildroot's .config
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Yann" == Yann E MORIN <[email protected]> writes:
Yann> Previously, the crosstool-NG backend did depend on the top-level Yann> Buildroot's .config to detect changes in the toolchain options, Yann> using a tentatively-clever heuristic, which also included the full Yann> Buildroot's version string to push down to set the components' versions Yann> strings.
Yann> In doing so, any commit in the Buildroot tree would imply a complete Yann> rebuild of the toolchain, even in the case the toolchain options did Yann> not change, thus being a large annoyance (to say the least).
Yann> As Buildroot never guaranteed that toolchain options would be detected, Yann> even less handled, and that the internal backend does neither detect nor Yann> act on toolchain options changes, and delegate that to the user, there Yann> is no point in individualising the crosstool-NG backend's behaviour.
Yann> This reasoning also applies to the depdency on the crosstool-NG's bundled Yann> .config file, too.
Yann> So, just drop the not-so-clever heuristic, and just build the toolchain Yann> once, leaving to the user the responsibility to explictly ask Buildroot Yann> to rebuild the toolchain.
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 1/1 toolchain/crosstool-NG: do not depend on the top-level Buildroot's .config
In reply to Yann E. MORINHello Yann,
Quoted 15 lines · On Monday 18 March 2013 23:03:03 Yann E. MORIN wrote:
Previously, the crosstool-NG backend did depend on the top-level Buildroot's .config to detect changes in the toolchain options, using a tentatively-clever heuristic, which also included the full Buildroot's version string to push down to set the components' versions strings.
In doing so, any commit in the Buildroot tree would imply a complete rebuild of the toolchain, even in the case the toolchain options did not change, thus being a large annoyance (to say the least).
As Buildroot never guaranteed that toolchain options would be detected, even less handled, and that the internal backend does neither detect nor act on toolchain options changes, and delegate that to the user, there is no point in individualising the crosstool-NG backend's behaviour.
Quoted 6 lines
This reasoning also applies to the depdency on the crosstool-NG's bundled .config file, too.
So, just drop the not-so-clever heuristic, and just build the toolchain once, leaving to the user the responsibility to explictly ask Buildroot to rebuild the toolchain.
Hmmm... I didn't followed all debate, and I am sorry if this suggestion has already been submitted but, why not depend on build/buildroot-config/br2/toolchain/ctng* ?
BR,
Signature · 3 lines
J?r?me Pouiller, Sysmic Embedded Linux specialist http://www.sysmic.fr
PATCH 1/1 toolchain/crosstool-NG: do not depend on the top-level Buildroot's .config
Dear J?r?me Pouiller,
Quoted 6 lines · J?r?me Pouiller
Quoted 3 lines
So, just drop the not-so-clever heuristic, and just build the toolchain once, leaving to the user the responsibility to explictly ask Buildroot to rebuild the toolchain.
Hmmm... I didn't followed all debate, and I am sorry if this suggestion has already been submitted but, why not depend on build/buildroot-config/br2/toolchain/ctng* ?
There's a choice:
1) Either we do detect changes in the configuration and automatically rebuild what needs to be rebuild. But if we decide to do that, we must do it *perfectly*. If we tell users "you can make changes in your configuration, run 'make' and it will automatically rebuild what's necessary", it should work perfectly, and not have some bizarre cases where it doesn't rebuild what's needed.
2) Or we don't even try to detect changes, even in simple cases. This keeps Buildroot simple and we have a simple thing to explain to our
users: "Buildroot doesn't try to detect which configuration changes you made, it's up to you to rebuild what's necessary, or restart a full build".
Until now, all the Buildroot developers agreed that (2) was the way to go. (1) is complicated to achieve correctly, and would add a significant complexity to Buildroot, which is something we absolutely want to avoid.
Best regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com