ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-22 22:22:23 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
2b2ec4dd4b
crosstool-ng/config/global/paths.in

91 lines
2.8 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
default n 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.
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
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
default "${CT_TOP_DIR}/targets"
help
Set this to the directory where all build actions will be done.
The default is "${CT_TOP_DIR}/targets", and leaving this option
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 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.
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.
Usefull 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