ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-24 15:06:42 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
581e8a514b
crosstool-ng/config/global/paths.in

116 lines
3.6 KiB
Plaintext
Raw Normal View History

Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
# Options related to paths and install
comment "Paths"
config LOCAL_TARBALLS_DIR
string
Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 06:51:05 +00:00
prompt "Local tarballs directory"
Simplify config saving. Instead of hardcoding defaults in saveSample.sh.in, have the same defaults in config. Then we can just remove them when saving the config.
2016-12-14 02:40:47 +00:00
default "${HOME}/src"
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
help
If you have previously downloaded the tarballs, enter the PATH where
you stored them here.
config SAVE_TARBALLS
bool
Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 06:51:05 +00:00
prompt "Save new tarballs"
depends on LOCAL_TARBALLS_DIR != ""
Simplify config saving. Instead of hardcoding defaults in saveSample.sh.in, have the same defaults in config. Then we can just remove them when saving the config.
2016-12-14 02:40:47 +00:00
default y
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
help
If you say 'y' here, new downloaded tarballs will be saved in the
directory you entered above.
Allow to store working files outside the build tree (eg. incase the working tree is on the network). /trunk/scripts/crosstool.sh | 9 5 4 0 +++++---- /trunk/config/global/paths.in | 23 22 1 0 ++++++++++++++++++++++- 2 files changed, 27 insertions(+), 5 deletions(-)
2008-06-24 16:19:45 +00:00
config WORK_DIR
string
Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 06:51:05 +00:00
prompt "Working directory"
config: change name of default build dir 'targets' is not really meaningfull. 'build' means what it means. '.build' just hides it as well! :-) Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-09-12 19:38:12 +00:00
default "${CT_TOP_DIR}/.build"
Allow to store working files outside the build tree (eg. incase the working tree is on the network). /trunk/scripts/crosstool.sh | 9 5 4 0 +++++---- /trunk/config/global/paths.in | 23 22 1 0 ++++++++++++++++++++++- 2 files changed, 27 insertions(+), 5 deletions(-)
2008-06-24 16:19:45 +00:00
help
Set this to the directory where all build actions will be done.
config: small help fix up for work dir default Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-04-27 23:10:23 +00:00
The default is "${CT_TOP_DIR}/.build", and leaving this option
Allow to store working files outside the build tree (eg. incase the working tree is on the network). /trunk/scripts/crosstool.sh | 9 5 4 0 +++++---- /trunk/config/global/paths.in | 23 22 1 0 ++++++++++++++++++++++- 2 files changed, 27 insertions(+), 5 deletions(-)
2008-06-24 16:19:45 +00:00
empty will also use the default.
You should not need to change that, except in one very peculiar
setup:
- your crosstool-NG source directory is on the network
- you configured crosstool-NG with --local
This kind of setup is a pain, as any action involving source file
access would have to go through the wire. In this case, you should
set CT_WORK_DIR to point to a path local to your machine, to avoid
any network overhead.
Do *NOT* change it if you don't know better.
Make build-all rely on kconfig options. For that, make CT_BUILD_TOP_DIR a non-settable config option (so that it is recursively expanded with CT_HOST/CT_TARGET). Use a common prefix, with same default as for regular sample build. Use showConfig.sh to determine host toolchain path (for canadian crosses) and build directory to be removed. Remove LIBC_SYSROOT_ARG (unused). Signed-off-by: Alexey Neyman <stilor@att.net>
2016-12-14 08:59:08 +00:00
config BUILD_TOP_DIR
string
default "${CT_WORK_DIR}/${CT_HOST:+HOST-${CT_HOST}/}${CT_TARGET}"
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config PREFIX_DIR
string
Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 06:51:05 +00:00
prompt "Prefix directory"
Make build-all rely on kconfig options. For that, make CT_BUILD_TOP_DIR a non-settable config option (so that it is recursively expanded with CT_HOST/CT_TARGET). Use a common prefix, with same default as for regular sample build. Use showConfig.sh to determine host toolchain path (for canadian crosses) and build directory to be removed. Remove LIBC_SYSROOT_ARG (unused). Signed-off-by: Alexey Neyman <stilor@att.net>
2016-12-14 08:59:08 +00:00
default "${CT_PREFIX:-${HOME}/x-tools}/${CT_HOST:+HOST-${CT_HOST}/}${CT_TARGET}"
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
help
This is the path the toolchain will run from.
config: add an option not to remove the destination directory In certain circumstances, removing the destination/installation directory is a bad idea. For example, when the build environment is already taking care of sanitising the build tree, and pre-installs stuff in there, it is a very bad idea to remove the destination directory. This happens now in buildroot, as the crostool-NG backend now installs the toolchain in the common host-tools directory, and pre-install there a few host-utilities (eg. host-automake and host-gawk). Provide a config knob to turn on/off the removal of the destination directory, defaulting to 'y' (previous behavior), and forced to 'n' when used as a backend. Reported-by: Peter Korsgaard <jacmet@sunsite.dk> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-01-28 21:06:49 +00:00
config RM_RF_PREFIX_DIR
bool
prompt "| Remove the prefix dir prior to building"
default y
help
If you say 'y' here, then PREFIX_DIR (above) will be eradicated
prior to the toolchain is built.
misc: fix more typos here and there... Reported-by: "Antony N. Pavlov" <antony@niisi.msk.ru> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-07-17 14:53:40 +00:00
This can be useful when you are trying different settings (due
config: add an option not to remove the destination directory In certain circumstances, removing the destination/installation directory is a bad idea. For example, when the build environment is already taking care of sanitising the build tree, and pre-installs stuff in there, it is a very bad idea to remove the destination directory. This happens now in buildroot, as the crostool-NG backend now installs the toolchain in the common host-tools directory, and pre-install there a few host-utilities (eg. host-automake and host-gawk). Provide a config knob to turn on/off the removal of the destination directory, defaulting to 'y' (previous behavior), and forced to 'n' when used as a backend. Reported-by: Peter Korsgaard <jacmet@sunsite.dk> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-01-28 21:06:49 +00:00
to build failures or feature tests). In this case, to avoid using
a potentially broken previous toolchain, the install location is
removed, to start afresh.
misc: fix more typos here and there... Reported-by: "Antony N. Pavlov" <antony@niisi.msk.ru> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-07-17 14:53:40 +00:00
On the other hand, if you are building a final toolchain, and install
config: add an option not to remove the destination directory In certain circumstances, removing the destination/installation directory is a bad idea. For example, when the build environment is already taking care of sanitising the build tree, and pre-installs stuff in there, it is a very bad idea to remove the destination directory. This happens now in buildroot, as the crostool-NG backend now installs the toolchain in the common host-tools directory, and pre-install there a few host-utilities (eg. host-automake and host-gawk). Provide a config knob to turn on/off the removal of the destination directory, defaulting to 'y' (previous behavior), and forced to 'n' when used as a backend. Reported-by: Peter Korsgaard <jacmet@sunsite.dk> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-01-28 21:06:49 +00:00
it into a directory with pre-install, unrelated programs, it would be
damageable to remove that directory. In this case, you may want to
say 'n' here.
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config REMOVE_DOCS
bool
prompt "Remove documentation"
Change some config items' default values. /trunk/config/global/paths.in | 4 2 2 0 ++-- /trunk/config/global/logging.in | 2 1 1 0 +- 2 files changed, 3 insertions(+), 3 deletions(-)
2008-08-01 08:23:29 +00:00
default y
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
help
Remove the installed documentation (man and info pages).
Gains around 8MiB for a uClibc-based, C and C++ compiler.
scripts: add support for building manuals Add support for building the HTML and PDF manuals for the major components. Implement for binutils, GCC, GDB, and GLIBC. Always build all manuals and install a subset. Be explicit about the subset to reduce the clutter and to avoid getting copies of common manuals like bfd from all of the sourceware based components. Downside of being explicit is that you need to update it when a new component comes along. Build the manuals as part of the last GCC build, namely 'cc' for glibc based ones and cc_core_pass_2 for baremetal. An example of the output is at: http://people.linaro.org/~michaelh/incoming/crosstool-NG/ Signed-off-by: Michael Hope <michael.hope@linaro.org> [yann.morin.1998@anciens.enib.fr: depends on ! remove docs; gold manual install] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-11-15 21:06:21 +00:00
config BUILD_MANUALS
bool
prompt "Build the manuals"
depends on ! REMOVE_DOCS
help
Build the PDF and HTML manuals for the main components such as
binutils, GCC, GDB, and the C library.
Kill CT_INSTALL_DIR. We now use CT_PREFIX and expect the resulting toolchain to be relocatable. Signed-off-by: Alexey Neyman <stilor@att.net>
2016-12-14 09:06:10 +00:00
config PREFIX_DIR_RO
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
bool
prompt "Render the toolchain read-only"
Change some config items' default values. /trunk/config/global/paths.in | 4 2 2 0 ++-- /trunk/config/global/logging.in | 2 1 1 0 +- 2 files changed, 3 insertions(+), 3 deletions(-)
2008-08-01 08:23:29 +00:00
default y
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
help
Render the directory of the toolchain (and its sub-directories)
read-only.
misc: fix more typos here and there... Reported-by: "Antony N. Pavlov" <antony@niisi.msk.ru> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-07-17 14:53:40 +00:00
Useful for toolchains destined for production.
scripts: add option to strip all toolchain executables To reduce filesizes of the toolchain and even improve build times of projects to be build with this toolchain it is usefull to strip the delivered toolchain executables. Since it is not likely that we will debug the toolchain executables itself we do not need the debug information inside the executables itself. Signed-off-by: Remy Bohmer <linux@bohmer.net>
2010-05-27 21:18:19 +00:00
Use install-strip target for gcc optionally
2015-11-10 09:59:02 +00:00
config STRIP_HOST_TOOLCHAIN_EXECUTABLES
scripts: add option to strip all toolchain executables To reduce filesizes of the toolchain and even improve build times of projects to be build with this toolchain it is usefull to strip the delivered toolchain executables. Since it is not likely that we will debug the toolchain executables itself we do not need the debug information inside the executables itself. Signed-off-by: Remy Bohmer <linux@bohmer.net>
2010-05-27 21:18:19 +00:00
bool
Use install-strip target for gcc optionally
2015-11-10 09:59:02 +00:00
prompt "Strip host toolchain executables"
scripts: add option to strip all toolchain executables To reduce filesizes of the toolchain and even improve build times of projects to be build with this toolchain it is usefull to strip the delivered toolchain executables. Since it is not likely that we will debug the toolchain executables itself we do not need the debug information inside the executables itself. Signed-off-by: Remy Bohmer <linux@bohmer.net>
2010-05-27 21:18:19 +00:00
default y
help
All build host executables contain a lot of unnecessary info.
Use install-strip target for gcc optionally
2015-11-10 09:59:02 +00:00
By stripping host executables it slightly speeds up the compilation
scripts: add option to strip all toolchain executables To reduce filesizes of the toolchain and even improve build times of projects to be build with this toolchain it is usefull to strip the delivered toolchain executables. Since it is not likely that we will debug the toolchain executables itself we do not need the debug information inside the executables itself. Signed-off-by: Remy Bohmer <linux@bohmer.net>
2010-05-27 21:18:19 +00:00
of large projects.
NOTE: It does NOT strip the target libraries, only HOST executables
Use install-strip target for gcc optionally
2015-11-10 09:59:02 +00:00
config STRIP_TARGET_TOOLCHAIN_EXECUTABLES
bool
prompt "Strip target toolchain executables"
help
It means using install-strip target for GCC 4.6 or later.
An install-strip make target is provided that installs stripped
executables, and may install libraries with unneeded or debugging
sections stripped.
Reference in New Issue Copy Permalink