ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-22 14:12:26 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
2cdbc6e370
crosstool-ng/config/config.mk

99 lines
4.4 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
KCONFIG_TOP = config/config.in
# 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
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
ARCH_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(wildcard $(CT_LIB_DIR)/config/arch/*.in))
ARCH_CONFIG_FILES_2 = $(patsubst $(CT_LIB_DIR)/%,%,$(wildcard $(CT_LIB_DIR)/config/arch/*.in.2))
KERNEL_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(wildcard $(CT_LIB_DIR)/config/kernel/*.in))
KERNEL_CONFIG_FILES_2 = $(patsubst $(CT_LIB_DIR)/%,%,$(wildcard $(CT_LIB_DIR)/config/kernel/*.in.2))
CC_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(wildcard $(CT_LIB_DIR)/config/cc/*.in))
CC_CONFIG_FILES_2 = $(patsubst $(CT_LIB_DIR)/%,%,$(wildcard $(CT_LIB_DIR)/config/cc/*.in.2))
LIBC_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(wildcard $(CT_LIB_DIR)/config/libc/*.in))
LIBC_CONFIG_FILES_2 = $(patsubst $(CT_LIB_DIR)/%,%,$(wildcard $(CT_LIB_DIR)/config/libc/*.in.2))
DEBUG_CONFIG_FILES = $(patsubst $(CT_LIB_DIR)/%,%,$(wildcard $(CT_LIB_DIR)/config/debug/*.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
GEN_CONFIG_FILES = config.gen/arch.in \
config.gen/kernel.in \
config.gen/cc.in \
config.gen/libc.in \
config.gen/debug.in
# ... 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:
@$(ECHO) " LN config"
$(SILENT)ln -s $(CT_LIB_DIR)/config config
# Where to store the generated config files into
config.gen:
@$(ECHO) " MKDIR config.gen"
$(SILENT)mkdir -p config.gen
#-----------------------------------------------------------
# Build list of per-component-type items to easily build generated files
ARCHS = $(patsubst config/arch/%.in,%,$(ARCH_CONFIG_FILES))
KERNELS = $(patsubst config/kernel/%.in,%,$(KERNEL_CONFIG_FILES))
CCS = $(patsubst config/cc/%.in,%,$(CC_CONFIG_FILES))
LIBCS = $(patsubst config/libc/%.in,%,$(LIBC_CONFIG_FILES))
DEBUGS = $(patsubst config/debug/%.in,%,$(DEBUG_CONFIG_FILES))
#-----------------------------------------------------------
# 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)
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
@$(ECHO) ' IN $(@)'
$(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)
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
@$(ECHO) ' IN $(@)'
$(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)
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
@$(ECHO) ' IN $(@)'
$(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
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)
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
@$(ECHO) ' IN $(@)'
$(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)
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
@$(ECHO) ' IN $(@)'
$(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
#-----------------------------------------------------------
# Cleaning up the mess...
clean::
@$(ECHO) " CLEAN config"
$(SILENT)rm -f config 2>/dev/null || true
@$(ECHO) " CLEAN config.gen"
$(SILENT)rm -rf config.gen
Reference in New Issue Copy Permalink