1 # Options related to paths and install
5 config LOCAL_TARBALLS_DIR
7 prompt "Local tarballs directory" if ! BACKEND
10 If you have previously downloaded the tarballs, enter the PATH where
15 prompt "Save new tarballs" if ! BACKEND
16 depends on LOCAL_TARBALLS_DIR != "" || BACKEND
19 If you say 'y' here, new downloaded tarballs will be saved in the
20 directory you entered above.
22 config CUSTOM_LOCATION_ROOT_DIR
24 depends on EXPERIMENTAL
25 prompt "Directory containing custom source components"
27 This is the path CT-NG will attempt to use as a root for locating
28 local copies of source components (CUSTOM_LOCATION_ROOT_DIR/component)
29 unless a component declares its own specific custom location.
33 prompt "Working directory" if ! BACKEND
34 default "${CT_TOP_DIR}/.build"
36 Set this to the directory where all build actions will be done.
38 The default is "${CT_TOP_DIR}/.build", and leaving this option
39 empty will also use the default.
41 You should not need to change that, except in one very peculiar
43 - your crosstool-NG source directory is on the network
44 - you configured crosstool-NG with --local
45 This kind of setup is a pain, as any action involving source file
46 access would have to go through the wire. In this case, you should
47 set CT_WORK_DIR to point to a path local to your machine, to avoid
50 Do *NOT* change it if you don't know better.
54 prompt "Prefix directory" if ! BACKEND
55 default "${HOME}/x-tools/${CT_TARGET}"
57 This is the path the toolchain will run from.
61 # prompt "Install directory"
62 default "${CT_PREFIX_DIR}"
64 # This is the path the toolchain will be installed into.
66 # Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
67 # you can't write there, you can install somewhere else and have a third
68 # person do the install for you.
69 # The reason you might also want to install elsewhere is if you are going
70 # to package your shinny new toolchain for distribution.
72 config RM_RF_PREFIX_DIR
74 prompt "| Remove the prefix dir prior to building"
78 If you say 'y' here, then PREFIX_DIR (above) will be eradicated
79 prior to the toolchain is built.
81 This can be useful when you are trying different settings (due
82 to build failures or feature tests). In this case, to avoid using
83 a potentially broken previous toolchain, the install location is
84 removed, to start afresh.
86 On the other hand, if you are building a final toolchain, and install
87 it into a directory with pre-install, unrelated programs, it would be
88 damageable to remove that directory. In this case, you may want to
91 Note that when acting as a backend, this option is not available, and
96 prompt "Remove documentation"
99 Remove the installed documentation (man and info pages).
100 Gains around 8MiB for a uClibc-based, C and C++ compiler.
104 prompt "Build the manuals"
105 depends on ! REMOVE_DOCS
107 Build the PDF and HTML manuals for the main components such as
108 binutils, GCC, GDB, and the C library.
110 config INSTALL_DIR_RO
112 prompt "Render the toolchain read-only"
115 Render the directory of the toolchain (and its sub-directories)
118 Useful for toolchains destined for production.
120 config STRIP_ALL_TOOLCHAIN_EXECUTABLES
122 prompt "Strip all toolchain executables"
125 All build host executables contain a lot of unnecessary info.
126 By stripping all executables it slightly speeds up the compilation
128 NOTE: It does NOT strip the target libraries, only HOST executables