1 # Options related to paths and install
5 config LOCAL_TARBALLS_DIR
7 prompt "Local tarballs directory"
10 If you have previously downloaded the tarballs, enter the PATH where
15 prompt "Save new tarballs"
17 depends on LOCAL_TARBALLS_DIR != ""
19 If you say 'y' here, new downloaded tarballs will be saved in the
20 directory you entered above.
24 prompt "Working directory"
25 default "${CT_TOP_DIR}/targets"
27 Set this to the directory where all build actions will be done.
29 The default is "${CT_TOP_DIR}/targets", and leaving this option
30 empty will also use the default.
32 You should not need to change that, except in one very peculiar
34 - your crosstool-NG source directory is on the network
35 - you configured crosstool-NG with --local
36 This kind of setup is a pain, as any action involving source file
37 access would have to go through the wire. In this case, you should
38 set CT_WORK_DIR to point to a path local to your machine, to avoid
41 Do *NOT* change it if you don't know better.
45 prompt "Prefix directory"
46 default "${HOME}/x-tools/${CT_TARGET}"
48 This is the path the toolchain will run from.
52 # prompt "Install directory"
53 default "${CT_PREFIX_DIR}"
55 # This is the path the toolchain will be installed into.
57 # Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
58 # you can't write there, you can install somewhere else and have a third
59 # person do the install for you.
60 # The reason you might also want to install elsewhere is if you are going
61 # to package your shinny new toolchain for distribution.
65 prompt "Remove documentation"
68 Remove the installed documentation (man and info pages).
69 Gains around 8MiB for a uClibc-based, C and C++ compiler.
73 prompt "Render the toolchain read-only"
76 Render the directory of the toolchain (and its sub-directories)
79 Usefull for toolchains destined for production.