yann@445: # Options related to paths and install
yann@1: 
yann@1: comment "Paths"
yann@1: 
yann@85: config LOCAL_TARBALLS_DIR
yann@1:     string
yann@1865:     prompt "Local tarballs directory" if ! BACKEND
yann@85:     default ""
yann@1:     help
yann@85:       If you have previously downloaded the tarballs, enter the PATH where
yann@85:       you stored them here.
yann@31: 
yann@265: config SAVE_TARBALLS
yann@265:     bool
yann@1865:     prompt "Save new tarballs" if ! BACKEND
yann@1865:     depends on LOCAL_TARBALLS_DIR != "" || BACKEND
yann@1865:     default y if BACKEND
yann@1865:     default n if ! BACKEND
yann@265:     help
yann@425:       If you say 'y' here, new downloaded tarballs will be saved in the
yann@265:       directory you entered above.
yann@265: 
yann@610: config WORK_DIR
yann@610:     string
yann@1865:     prompt "Working directory" if ! BACKEND
yann@2109:     default "${CT_TOP_DIR}/.build"
yann@610:     help
yann@610:       Set this to the directory where all build actions will be done.
yann@610:       
yann@610:       The default is "${CT_TOP_DIR}/targets", and leaving this option
yann@610:       empty will also use the default.
yann@610:       
yann@610:       You should not need to change that, except in one very peculiar
yann@610:       setup:
yann@610:        - your crosstool-NG source directory is on the network
yann@610:        - you configured crosstool-NG with --local
yann@610:       This kind of setup is a pain, as any action involving source file
yann@610:       access would have to go through the wire. In this case, you should
yann@610:       set CT_WORK_DIR to point to a path local to your machine, to avoid
yann@610:       any network overhead.
yann@610:       
yann@610:       Do *NOT* change it if you don't know better.
yann@610: 
yann@1: config PREFIX_DIR
yann@1:     string
yann@1865:     prompt "Prefix directory" if ! BACKEND
yann@613:     default "${HOME}/x-tools/${CT_TARGET}"
yann@1:     help
yann@1:       This is the path the toolchain will run from.
yann@1: 
yann@1: config INSTALL_DIR
yann@1:     string
yann@1: #    prompt "Install directory"
yann@1:     default "${CT_PREFIX_DIR}"
yann@1: #    help
yann@610: #      This is the path the toolchain will be installed into.
yann@1: #      
yann@1: #      Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
yann@1: #      you can't write there, you can install somewhere else and have a third
yann@1: #      person do the install for you.
yann@1: #      The reason you might also want to install elsewhere is if you are going
yann@1: #      to package your shinny new toolchain for distribution.
yann@1: 
yann@14: config REMOVE_DOCS
yann@14:     bool
yann@14:     prompt "Remove documentation"
yann@753:     default y
yann@14:     help
yann@14:       Remove the installed documentation (man and info pages).
yann@14:       Gains around 8MiB for a uClibc-based, C and C++ compiler.
yann@14: 
yann@174: config INSTALL_DIR_RO
yann@174:     bool
yann@174:     prompt "Render the toolchain read-only"
yann@753:     default y
yann@174:     help
yann@174:       Render the directory of the toolchain (and its sub-directories)
yann@174:       read-only.
yann@174:       
yann@174:       Usefull for toolchains destined for production.
linux@2060: 
linux@2060: config STRIP_ALL_TOOLCHAIN_EXECUTABLES
linux@2060:     bool
linux@2060:     prompt "Strip all toolchain executables"
linux@2060:     default y
linux@2060:     help
linux@2060:       All build host executables contain a lot of unnecessary info.
linux@2060:       By stripping all executables it slightly speeds up the compilation
linux@2060:       of large projects.
linux@2060:       NOTE: It does NOT strip the target libraries, only HOST executables