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(-)
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}/${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 "Use custom patch directory"
68 If you have custom patches that you want to be applied, say 'Y' here and
69 enter the path directory below.
71 Note that you must ensure that the patch directory is arranged the same
72 way the official directory is.
74 config CUSTOM_PATCH_ONLY
76 prompt "Only use custom patches"
78 depends on CUSTOM_PATCH
80 Don't apply patches coming with crosstool-NG, only those patches available
81 in the directory below.
83 If you say 'N' here, then the patches provided with crosstool-NG will be
84 applied first, and then your patches.
86 config CUSTOM_PATCH_DIR
88 prompt "Custom patch directory"
90 depends on CUSTOM_PATCH
92 Enter the custom patch directory here.
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.
102 config INSTALL_DIR_RO
104 prompt "Render the toolchain read-only"
107 Render the directory of the toolchain (and its sub-directories)
110 Usefull for toolchains destined for production.