ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-19 12:57:53 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
a08a4c4b88
crosstool-ng/config/config.mk

115 lines
5.7 KiB
Makefile
Raw Normal View History

Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
# ===========================================================================
# crosstool-NG genererated config files
# These targets are used from top-level makefile
#-----------------------------------------------------------
Enhance the make fragments: - comment the different parts - re-order the code so that it is homogeneous amogst fragments - eye-candy in some existing comments /trunk/tools/tools.mk | 17 15 2 0 +++++++++++++++-- /trunk/steps.mk | 38 26 12 0 ++++++++++++++++++++++++++------------ /trunk/samples/samples.mk | 41 28 13 0 ++++++++++++++++++++++++++++------------- /trunk/config/config.mk | 2 1 1 0 +- 4 files changed, 70 insertions(+), 28 deletions(-)
2008-10-27 18:42:26 +00:00
# List all config files, wether sourced or generated
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
# The top-level config file to be used be configurators
samples: use savedefconfig when saving samples When saving a sample, use savedefconfig instead of copying the full .config file. This reduces the saved .config, and reduces clutter when it is later upgraded. Also use defconfig when retrieving a sample. Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2012-05-06 22:27:05 +00:00
# We need it to savedefconfig in scripts/saveSample.sh
export KCONFIG_TOP = config/config.in
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
# Build the list of all source config files
config: add support for a second part of the generated choices Some components have configuration options that can depend on generic options, so they should go below those. uClibc for example: - has its own options (wchar...) - uses the generic options (threads...) - if linuxthreads chosen, offers two impls So we need to be able to split the components options in 2, one part that is above the generic options, and one part that ends up below the generic options.
2010-06-08 21:26:54 +00:00
STATIC_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(shell find $(CT_LIB_DIR)/config -type f \( -name '*.in' -o -name '*.in.2' \) 2>/dev/null))
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
# ... and how to access them:
$(STATIC_CONFIG_FILES): config
# Build a list of per-component-type source config files
all: fix wildcard to work with make-4.x In make-3.8x, the $(wildacrd) function would sort the entries, while in make-4.x, it would just return the entries in any unpredictable order [*] Use the $(sort) function to get reproducible behaviour. [*] Well, most probably the roder the entries appear when read from readdir() Reported-by: Andrew Ruder <andrew.ruder@elecsyscorp.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Tested-by: Andrew Ruder <andrew.ruder@elecsyscorp.com>
2014-06-25 21:33:01 +00:00
ARCH_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/arch/*.in)))
ARCH_CONFIG_FILES_2 = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/arch/*.in.2)))
KERNEL_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/kernel/*.in)))
KERNEL_CONFIG_FILES_2 = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/kernel/*.in.2)))
CC_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/cc/*.in)))
CC_CONFIG_FILES_2 = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/cc/*.in.2)))
BINUTILS_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/binutils/*.in)))
BINUTILS_CONFIG_FILES_2 = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/binutils/*.in.2)))
LIBC_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/libc/*.in)))
LIBC_CONFIG_FILES_2 = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/libc/*.in.2)))
DEBUG_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/debug/*.in)))
Give companion tools some love. Allow selection of make/m4/... version. Support imports of new versions via addToolVersion.sh. Import newest versions of the companion tools. One non-trivial change is the handling of make versions. Existing code was not handling make companion tool as described (see the previous commit). However, since most modern systems have make 4.x, that previous commit made crosstool-ng always build make as a companion tool. This traces back to the commit dd15c93 from 2014. That commit's log message says that actually it was 3.81 which broke the build for certain component (it was originally breaking eglibc, but I noticed it was breaking current glibc on powerpc64), and introduced an option to force using 3.81 by "components that really need it". It looks like in 2.5 years we haven't seen any such components that really need make 3.81, and (given that make has already had a few releases since 3.81) we're unlikely to see them in the future. Hence, the configure check is changed from "exactly 3.81" to "3.81 or newer". In its current form, configure will accept make 3.80+, and will not require make as a companion tool for 3.81+. We might want to bump the latter check to even newer version given the claim from dd15c93. Killed COMP_TOOLS_make_3_81_NEEDED. Anyway, I retained 3.81 just in case; ditto for m4 1.14.3, autoconf 2.65 and automake 1.11.1. Signed-off-by: Alexey Neyman <stilor@att.net>
2016-11-21 20:09:54 +00:00
COMP_TOOLS_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(sort $(wildcard $(CT_LIB_DIR)/config/companion_tools/*.in)))
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
# Build the list of generated config files
Give companion tools some love. Allow selection of make/m4/... version. Support imports of new versions via addToolVersion.sh. Import newest versions of the companion tools. One non-trivial change is the handling of make versions. Existing code was not handling make companion tool as described (see the previous commit). However, since most modern systems have make 4.x, that previous commit made crosstool-ng always build make as a companion tool. This traces back to the commit dd15c93 from 2014. That commit's log message says that actually it was 3.81 which broke the build for certain component (it was originally breaking eglibc, but I noticed it was breaking current glibc on powerpc64), and introduced an option to force using 3.81 by "components that really need it". It looks like in 2.5 years we haven't seen any such components that really need make 3.81, and (given that make has already had a few releases since 3.81) we're unlikely to see them in the future. Hence, the configure check is changed from "exactly 3.81" to "3.81 or newer". In its current form, configure will accept make 3.80+, and will not require make as a companion tool for 3.81+. We might want to bump the latter check to even newer version given the claim from dd15c93. Killed COMP_TOOLS_make_3_81_NEEDED. Anyway, I retained 3.81 just in case; ditto for m4 1.14.3, autoconf 2.65 and automake 1.11.1. Signed-off-by: Alexey Neyman <stilor@att.net>
2016-11-21 20:09:54 +00:00
GEN_CONFIG_FILES = config.gen/arch.in \
config.gen/kernel.in \
config.gen/cc.in \
config.gen/binutils.in \
config.gen/libc.in \
config.gen/debug.in \
config.gen/companion_tools.in
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
# ... and how to access them:
config: move multi-line shell commands from Makefile to script Maintaining thos multi-line shell commands in a Makefile rule is a real PITA. Move the two affected rules (build_gen_choice_in and build_gen_menu_in to a shell script. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-07-03 21:02:16 +00:00
# Generated files depends on the gen_in_frags script because it has the
# functions needed to build the genrated files, and thus they might need
# re-generation if it changes.
# They also depends on config.mk (this file) because it has the dependency
# rules, and thus they might need re-generation if the deps change.
$(GEN_CONFIG_FILES): config.gen \
$(CT_LIB_DIR)/scripts/gen_in_frags.sh \
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
$(CT_LIB_DIR)/config/config.mk
# Helper entry for the configurators
PHONY += config_files
config_files: $(STATIC_CONFIG_FILES) $(GEN_CONFIG_FILES)
# Where to access to the source config files from
config:
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) " LN config"
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
$(SILENT)ln -s $(CT_LIB_DIR)/config config
# Where to store the generated config files into
config.gen:
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) " MKDIR config.gen"
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
$(SILENT)mkdir -p config.gen
#-----------------------------------------------------------
# Build list of per-component-type items to easily build generated files
scripts: fix mis-alignment due to new variables Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2012-11-19 21:13:11 +00:00
ARCHS = $(patsubst config/arch/%.in,%,$(ARCH_CONFIG_FILES))
KERNELS = $(patsubst config/kernel/%.in,%,$(KERNEL_CONFIG_FILES))
CCS = $(patsubst config/cc/%.in,%,$(CC_CONFIG_FILES))
binutils: introduce the infrastructure to support binutils alternatives Rework binutils in order to provide soon binutils alternative. Signed-off-by: Yann Diorcet <diorcet.yann@gmail.com> [yann.morin.1998@free.fr: split up original patch for self-contained changes] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local> Patchwork-Id: 199971
2012-11-19 10:21:31 +00:00
BINUTILSS = $(patsubst config/binutils/%.in,%,$(BINUTILS_CONFIG_FILES))
scripts: fix mis-alignment due to new variables Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2012-11-19 21:13:11 +00:00
LIBCS = $(patsubst config/libc/%.in,%,$(LIBC_CONFIG_FILES))
DEBUGS = $(patsubst config/debug/%.in,%,$(DEBUG_CONFIG_FILES))
Give companion tools some love. Allow selection of make/m4/... version. Support imports of new versions via addToolVersion.sh. Import newest versions of the companion tools. One non-trivial change is the handling of make versions. Existing code was not handling make companion tool as described (see the previous commit). However, since most modern systems have make 4.x, that previous commit made crosstool-ng always build make as a companion tool. This traces back to the commit dd15c93 from 2014. That commit's log message says that actually it was 3.81 which broke the build for certain component (it was originally breaking eglibc, but I noticed it was breaking current glibc on powerpc64), and introduced an option to force using 3.81 by "components that really need it". It looks like in 2.5 years we haven't seen any such components that really need make 3.81, and (given that make has already had a few releases since 3.81) we're unlikely to see them in the future. Hence, the configure check is changed from "exactly 3.81" to "3.81 or newer". In its current form, configure will accept make 3.80+, and will not require make as a companion tool for 3.81+. We might want to bump the latter check to even newer version given the claim from dd15c93. Killed COMP_TOOLS_make_3_81_NEEDED. Anyway, I retained 3.81 just in case; ditto for m4 1.14.3, autoconf 2.65 and automake 1.11.1. Signed-off-by: Alexey Neyman <stilor@att.net>
2016-11-21 20:09:54 +00:00
COMP_TOOLS= $(patsubst config/companion_tools/%.in,%,$(COMP_TOOLS_CONFIG_FILES))
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
#-----------------------------------------------------------
# The rules for the generated config files
config: add support for a second part of the generated choices Some components have configuration options that can depend on generic options, so they should go below those. uClibc for example: - has its own options (wchar...) - uses the generic options (threads...) - if linuxthreads chosen, offers two impls So we need to be able to split the components options in 2, one part that is above the generic options, and one part that ends up below the generic options.
2010-06-08 21:26:54 +00:00
# WARNING! If a .in file disapears between two runs, that will NOT be detected!
config.gen/arch.in: $(ARCH_CONFIG_FILES) $(ARCH_CONFIG_FILES_2)
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) ' IN $(@)'
config: move multi-line shell commands from Makefile to script Maintaining thos multi-line shell commands in a Makefile rule is a real PITA. Move the two affected rules (build_gen_choice_in and build_gen_menu_in to a shell script. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-07-03 21:02:16 +00:00
$(SILENT)$(CT_LIB_DIR)/scripts/gen_in_frags.sh choice "$@" "Target Architecture" "ARCH" "config/arch" "Y" $(ARCHS)
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
config: add support for a second part of the generated choices Some components have configuration options that can depend on generic options, so they should go below those. uClibc for example: - has its own options (wchar...) - uses the generic options (threads...) - if linuxthreads chosen, offers two impls So we need to be able to split the components options in 2, one part that is above the generic options, and one part that ends up below the generic options.
2010-06-08 21:26:54 +00:00
config.gen/kernel.in: $(KERNEL_CONFIG_FILES) $(KERNEL_CONFIG_FILES_2)
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) ' IN $(@)'
config: move multi-line shell commands from Makefile to script Maintaining thos multi-line shell commands in a Makefile rule is a real PITA. Move the two affected rules (build_gen_choice_in and build_gen_menu_in to a shell script. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-07-03 21:02:16 +00:00
$(SILENT)$(CT_LIB_DIR)/scripts/gen_in_frags.sh choice "$@" "Target OS" "KERNEL" "config/kernel" "Y" $(KERNELS)
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
config: add support for a second part of the generated choices Some components have configuration options that can depend on generic options, so they should go below those. uClibc for example: - has its own options (wchar...) - uses the generic options (threads...) - if linuxthreads chosen, offers two impls So we need to be able to split the components options in 2, one part that is above the generic options, and one part that ends up below the generic options.
2010-06-08 21:26:54 +00:00
config.gen/cc.in: $(CC_CONFIG_FILES) $(CC_CONFIG_FILES_2)
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) ' IN $(@)'
config: move multi-line shell commands from Makefile to script Maintaining thos multi-line shell commands in a Makefile rule is a real PITA. Move the two affected rules (build_gen_choice_in and build_gen_menu_in to a shell script. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-07-03 21:02:16 +00:00
$(SILENT)$(CT_LIB_DIR)/scripts/gen_in_frags.sh choice "$@" "C compiler" "CC" "config/cc" "N" $(CCS)
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
binutils: introduce the infrastructure to support binutils alternatives Rework binutils in order to provide soon binutils alternative. Signed-off-by: Yann Diorcet <diorcet.yann@gmail.com> [yann.morin.1998@free.fr: split up original patch for self-contained changes] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local> Patchwork-Id: 199971
2012-11-19 10:21:31 +00:00
config.gen/binutils.in: $(CC_BINUTILS_FILES) $(CC_BINUTILS_FILES_2)
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) ' IN $(@)'
binutils: introduce the infrastructure to support binutils alternatives Rework binutils in order to provide soon binutils alternative. Signed-off-by: Yann Diorcet <diorcet.yann@gmail.com> [yann.morin.1998@free.fr: split up original patch for self-contained changes] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local> Patchwork-Id: 199971
2012-11-19 10:21:31 +00:00
$(SILENT)$(CT_LIB_DIR)/scripts/gen_in_frags.sh choice "$@" "Binutils" "BINUTILS" "config/binutils" "N" $(BINUTILSS)
config: add support for a second part of the generated choices Some components have configuration options that can depend on generic options, so they should go below those. uClibc for example: - has its own options (wchar...) - uses the generic options (threads...) - if linuxthreads chosen, offers two impls So we need to be able to split the components options in 2, one part that is above the generic options, and one part that ends up below the generic options.
2010-06-08 21:26:54 +00:00
config.gen/libc.in: $(LIBC_CONFIG_FILES) $(LIBC_CONFIG_FILES_2)
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) ' IN $(@)'
config: move multi-line shell commands from Makefile to script Maintaining thos multi-line shell commands in a Makefile rule is a real PITA. Move the two affected rules (build_gen_choice_in and build_gen_menu_in to a shell script. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-07-03 21:02:16 +00:00
$(SILENT)$(CT_LIB_DIR)/scripts/gen_in_frags.sh choice "$@" "C library" "LIBC" "config/libc" "Y" $(LIBCS)
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
config.gen/debug.in: $(DEBUG_CONFIG_FILES)
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) ' IN $(@)'
config: move multi-line shell commands from Makefile to script Maintaining thos multi-line shell commands in a Makefile rule is a real PITA. Move the two affected rules (build_gen_choice_in and build_gen_menu_in to a shell script. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-07-03 21:02:16 +00:00
$(SILENT)$(CT_LIB_DIR)/scripts/gen_in_frags.sh menu "$@" "Debug facilities" "DEBUG" "config/debug" $(DEBUGS)
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
Give companion tools some love. Allow selection of make/m4/... version. Support imports of new versions via addToolVersion.sh. Import newest versions of the companion tools. One non-trivial change is the handling of make versions. Existing code was not handling make companion tool as described (see the previous commit). However, since most modern systems have make 4.x, that previous commit made crosstool-ng always build make as a companion tool. This traces back to the commit dd15c93 from 2014. That commit's log message says that actually it was 3.81 which broke the build for certain component (it was originally breaking eglibc, but I noticed it was breaking current glibc on powerpc64), and introduced an option to force using 3.81 by "components that really need it". It looks like in 2.5 years we haven't seen any such components that really need make 3.81, and (given that make has already had a few releases since 3.81) we're unlikely to see them in the future. Hence, the configure check is changed from "exactly 3.81" to "3.81 or newer". In its current form, configure will accept make 3.80+, and will not require make as a companion tool for 3.81+. We might want to bump the latter check to even newer version given the claim from dd15c93. Killed COMP_TOOLS_make_3_81_NEEDED. Anyway, I retained 3.81 just in case; ditto for m4 1.14.3, autoconf 2.65 and automake 1.11.1. Signed-off-by: Alexey Neyman <stilor@att.net>
2016-11-21 20:09:54 +00:00
config.gen/companion_tools.in: $(COMP_TOOLS_CONFIG_FILES)
@$(CT_ECHO) ' IN $(@)'
$(SILENT)$(CT_LIB_DIR)/scripts/gen_in_frags.sh menu "$@" "Companion tools" "COMP_TOOLS" "config/companion_tools" $(COMP_TOOLS)
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
#-----------------------------------------------------------
# Cleaning up the mess...
clean::
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) " CLEAN config"
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
$(SILENT)rm -f config 2>/dev/null || true
Fix samples using GMP 4.3.2. Some older versions of configure (including the one in GMP 4.3.2) interpret the $ECHO environment variable as the `echo' utility to use. CT-NG sets the variable to `:' and exports it if V=0 or V=1 is supplied, breaking the samples using such configure. This currently includes bfin-unknown-linux-uclibc and powerpc-unknown-linux-uclibc. Also, correct the description of the V= variable - V=0 is *not* the default; in fact, default does not correspond to any of the V=[012] values. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-30 02:34:24 +00:00
@$(CT_ECHO) " CLEAN config.gen"
Extract the config files related stuff from the kconfig stuff - create config/config.mk, with all the config.gen/ rules - the only common points between config files and configurators: - the top-level config file to include, stored in KCONFIG_TOP - the config_file rules, which makes config files available to configurators - dependency-files are renamed from %.d to %.dep (.d is reserved for directories) - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 184 12 172 0 +++-------------------------------------------------- /trunk/config/config.mk | 118 9 109 0 +++------------------------------- /trunk/ct-ng.in | 1 1 0 0 + 3 files changed, 22 insertions(+), 281 deletions(-)
2008-10-18 18:37:28 +00:00
$(SILENT)rm -rf config.gen
Reference in New Issue Copy Permalink