ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-25 07:21:05 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
fc4d1bf65f
crosstool-ng/config/global/paths.in

129 lines
4.2 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
config: hide paths when used as a backend When crosstool-NG is used as a backend, it is the responsibility of the upper-layer build-system to properly set paths, so we just hide the prompts in this case.
2010-03-29 10:04:27 +00:00
prompt "Local tarballs directory" if ! BACKEND
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
default ""
help
If you have previously downloaded the tarballs, enter the PATH where
you stored them here.
config SAVE_TARBALLS
bool
config: hide paths when used as a backend When crosstool-NG is used as a backend, it is the responsibility of the upper-layer build-system to properly set paths, so we just hide the prompts in this case.
2010-03-29 10:04:27 +00:00
prompt "Save new tarballs" if ! BACKEND
depends on LOCAL_TARBALLS_DIR != "" || BACKEND
default y if BACKEND
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.
scripts/functions: add a generic custom location infrastructure Add a generic custom location infrastructure (inspired by the one in kernel/linux) to allow the user to use custom tarballs or directories for any component. Signed-off-by: "David Holsgrove" <david.holsgrove@xilinx.com> [yann.morin.1998@free.fr: move config option, improve help text, fix API doc] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Message-Id: <131c163c69f9cc81d2be.1349931191@localhost.localdomain> PatchWork-Id: 190784 Message-Id: <0bbaba9190a76ba97f72.1349931192@localhost.localdomain> PatchWork-Id: 190785
2012-10-04 03:26:14 +00:00
config CUSTOM_LOCATION_ROOT_DIR
string
depends on EXPERIMENTAL
prompt "Directory containing custom source components"
help
This is the path CT-NG will attempt to use as a root for locating
local copies of source components (CUSTOM_LOCATION_ROOT_DIR/component)
unless a component declares its own specific custom location.
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
config: hide paths when used as a backend When crosstool-NG is used as a backend, it is the responsibility of the upper-layer build-system to properly set paths, so we just hide the prompts in this case.
2010-03-29 10:04:27 +00:00
prompt "Working directory" if ! BACKEND
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.
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
config: hide paths when used as a backend When crosstool-NG is used as a backend, it is the responsibility of the upper-layer build-system to properly set paths, so we just hide the prompts in this case.
2010-03-29 10:04:27 +00:00
prompt "Prefix directory" if ! BACKEND
Change default path where toolchain will run from to "${HOME}/x-tools/${CT_TARGET}". /trunk/config/global/paths.in | 2 1 1 0 +- 1 file changed, 1 insertion(+), 1 deletion(-)
2008-06-25 06:24:51 +00:00
default "${HOME}/x-tools/${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 INSTALL_DIR
string
# prompt "Install directory"
default "${CT_PREFIX_DIR}"
# help
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
# This is the path the toolchain will be installed into.
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
#
# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
# you can't write there, you can install somewhere else and have a third
# person do the install for you.
# The reason you might also want to install elsewhere is if you are going
# to package your shinny new toolchain for distribution.
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
depends on !BACKEND
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.
Note that when acting as a backend, this option is not available, and
is forced to 'n'.
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.
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 INSTALL_DIR_RO
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
config STRIP_ALL_TOOLCHAIN_EXECUTABLES
bool
prompt "Strip all toolchain executables"
default y
help
All build host executables contain a lot of unnecessary info.
By stripping all executables it slightly speeds up the compilation
of large projects.
NOTE: It does NOT strip the target libraries, only HOST executables
Reference in New Issue Copy Permalink