ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-20 05:17:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
27e8b280f9
crosstool-ng/kconfig/kconfig.mk

52 lines
2.0 KiB
Makefile
Raw Normal View History

Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
# ===========================================================================
Get rid of eclipse fiels once and for all. Homogenise the references to crosstool-NG: - the project is named "crosstool-NG" - the front-end is named "ct-ng" - don't use shortcuts (such as "ct-ng" to stand for "crosstool-NG") Default action is to print help. Don't speak of make rules when dumping help, just speak of actions.
2007-07-02 19:40:54 +00:00
# crosstool-NG configuration targets
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
# These targets are used from top-level makefile
Rework the kconfig stuff - better handle config file generation dependencies - get rid of CT_TOP_DIR where useless - rearrange code to be cleaner, and add adequate '#----' comments to split the different parts - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 158 99 59 0 +++++++++++++++++++++++++++++++++-------------------- 1 file changed, 99 insertions(+), 59 deletions(-)
2008-10-14 16:50:33 +00:00
#-----------------------------------------------------------
# The configurators rules
Merge the build system to trunk: ct-ng is now installable: - ./configure --prefix=/some/place - make - make install - export PATH="${PATH}:/some/place/bin" - ct-ng <action>
2007-07-01 19:04:20 +00:00
kconfig: add the nconf frontend The nconf frontend is the new hot topic in the kconfig land! :-) Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-05-12 17:45:30 +00:00
configurators = menuconfig nconfig oldconfig
Avoid (re)building the kconfig dependencies when we don't need them (clean, build, list-steps...). /trunk/kconfig/kconfig.mk | 24 20 4 0 ++++++++++++++++++++---- 1 file changed, 20 insertions(+), 4 deletions(-)
2008-10-19 09:34:32 +00:00
PHONY += $(configurators)
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
Avoid (re)building the kconfig dependencies when we don't need them (clean, build, list-steps...). /trunk/kconfig/kconfig.mk | 24 20 4 0 ++++++++++++++++++++---- 1 file changed, 20 insertions(+), 4 deletions(-)
2008-10-19 09:34:32 +00:00
$(configurators): config_files
kconfig: install compiled frontends The kconfig frontends are currently instaleld as source files. This is a remnant of the early times, when I wanted a single installation of crosstool-NG to be shared across multiple machines, potentially of different architectures. This does not really make sense, and it's been a long time since it was las tpossible in practice. So, just build the kconfig frontends at make-time, and install them as we do for all other crosstool-NG dependent files. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2012-01-14 17:22:06 +00:00
CONF := $(CT_LIB_DIR)/kconfig/conf
MCONF := $(CT_LIB_DIR)/kconfig/mconf
NCONF := $(CT_LIB_DIR)/kconfig/nconf
menuconfig:
Enhance the kconfig stuff build procedure: - better allocate CFLAGS/LDFLAGS to object and dependency files - only include the needed dependency files - cleanly handle the kconfig/ check and creation - use HOST_LD to link, not HOST_CC (even if both are set to 'gcc' for now) - get rid of defoldconfig, it does not make much sense using it. /trunk/kconfig/kconfig.mk | 110 66 44 0 ++++++++++++++++++++++++++++++++--------------------- 1 file changed, 66 insertions(+), 44 deletions(-)
2008-10-22 16:56:23 +00:00
@$(ECHO) " CONF $(KCONFIG_TOP)"
kconfig: install compiled frontends The kconfig frontends are currently instaleld as source files. This is a remnant of the early times, when I wanted a single installation of crosstool-NG to be shared across multiple machines, potentially of different architectures. This does not really make sense, and it's been a long time since it was las tpossible in practice. So, just build the kconfig frontends at make-time, and install them as we do for all other crosstool-NG dependent files. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2012-01-14 17:22:06 +00:00
$(SILENT)$(MCONF) $(KCONFIG_TOP)
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
kconfig: install compiled frontends The kconfig frontends are currently instaleld as source files. This is a remnant of the early times, when I wanted a single installation of crosstool-NG to be shared across multiple machines, potentially of different architectures. This does not really make sense, and it's been a long time since it was las tpossible in practice. So, just build the kconfig frontends at make-time, and install them as we do for all other crosstool-NG dependent files. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2012-01-14 17:22:06 +00:00
nconfig:
kconfig: add the nconf frontend The nconf frontend is the new hot topic in the kconfig land! :-) Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-05-12 17:45:30 +00:00
@$(ECHO) " CONF $(KCONFIG_TOP)"
kconfig: install compiled frontends The kconfig frontends are currently instaleld as source files. This is a remnant of the early times, when I wanted a single installation of crosstool-NG to be shared across multiple machines, potentially of different architectures. This does not really make sense, and it's been a long time since it was las tpossible in practice. So, just build the kconfig frontends at make-time, and install them as we do for all other crosstool-NG dependent files. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2012-01-14 17:22:06 +00:00
$(SILENT)$(NCONF) $(KCONFIG_TOP)
kconfig: add the nconf frontend The nconf frontend is the new hot topic in the kconfig land! :-) Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-05-12 17:45:30 +00:00
kconfig: install compiled frontends The kconfig frontends are currently instaleld as source files. This is a remnant of the early times, when I wanted a single installation of crosstool-NG to be shared across multiple machines, potentially of different architectures. This does not really make sense, and it's been a long time since it was las tpossible in practice. So, just build the kconfig frontends at make-time, and install them as we do for all other crosstool-NG dependent files. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2012-01-14 17:22:06 +00:00
oldconfig: .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
@$(ECHO) " CONF $(KCONFIG_TOP)"
kconfig: install compiled frontends The kconfig frontends are currently instaleld as source files. This is a remnant of the early times, when I wanted a single installation of crosstool-NG to be shared across multiple machines, potentially of different architectures. This does not really make sense, and it's been a long time since it was las tpossible in practice. So, just build the kconfig frontends at make-time, and install them as we do for all other crosstool-NG dependent files. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2012-01-14 17:22:06 +00:00
$(SILENT)$(CONF) --silent$@ $(KCONFIG_TOP)
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
scripts: add action to extract config from a build.log file That got removed quite some time ago, but is really usefull to get the configuration from a build.log file of a failing build.
2010-02-11 20:28:10 +00:00
# Always be silent, the stdout an be >.config
extractconfig:
@awk 'BEGIN { dump=0; } \
dump==1 && $$0~/^\[.....\][[:space:]]+(# |)CT_/ { \
$$1=""; \
gsub("^[[:space:]]",""); \
print; \
} \
$$0~/Dumping user-supplied crosstool-NG configuration: done in/ { \
dump=0; \
} \
$$0~/Dumping user-supplied crosstool-NG configuration$$/ { \
dump=1; \
}'
Rework the kconfig stuff - better handle config file generation dependencies - get rid of CT_TOP_DIR where useless - rearrange code to be cleaner, and add adequate '#----' comments to split the different parts - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 158 99 59 0 +++++++++++++++++++++++++++++++++-------------------- 1 file changed, 99 insertions(+), 59 deletions(-)
2008-10-14 16:50:33 +00:00
#-----------------------------------------------------------
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
# Help text used by make help
Rework the kconfig stuff - better handle config file generation dependencies - get rid of CT_TOP_DIR where useless - rearrange code to be cleaner, and add adequate '#----' comments to split the different parts - a few eye-candy here and there /trunk/kconfig/kconfig.mk | 158 99 59 0 +++++++++++++++++++++++++++++++++-------------------- 1 file changed, 99 insertions(+), 59 deletions(-)
2008-10-14 16:50:33 +00:00
Rework the help system. For now, this is mostly a no-op (it only re-organise the help entries), but later, that may come in handy when we want ct-ng to be installable).
2007-06-17 16:24:23 +00:00
help-config::
Add the possibility to force the number of // jobs without reconfiguring.
2007-08-15 14:59:37 +00:00
@echo ' menuconfig - Update current config using a menu based program'
@echo ' oldconfig - Update current config using a provided .config as base'
scripts: add action to extract config from a build.log file That got removed quite some time ago, but is really usefull to get the configuration from a build.log file of a failing build.
2010-02-11 20:28:10 +00:00
@echo ' extractconfig - Extract to stdout the configuration items from a'
@echo ' build.log file piped to stdin'
Reference in New Issue Copy Permalink