|
yann@445
|
1 |
# Options related to paths and install
|
|
yann@1
|
2 |
|
|
yann@1
|
3 |
comment "Paths"
|
|
yann@1
|
4 |
|
|
yann@85
|
5 |
config LOCAL_TARBALLS_DIR
|
|
yann@1
|
6 |
string
|
|
yann@85
|
7 |
prompt "Local tarballs directory"
|
|
yann@85
|
8 |
default ""
|
|
yann@1
|
9 |
help
|
|
yann@85
|
10 |
If you have previously downloaded the tarballs, enter the PATH where
|
|
yann@85
|
11 |
you stored them here.
|
|
yann@31
|
12 |
|
|
yann@265
|
13 |
config SAVE_TARBALLS
|
|
yann@265
|
14 |
bool
|
|
yann@265
|
15 |
prompt "Save new tarballs"
|
|
yann@265
|
16 |
default n
|
|
yann@265
|
17 |
depends on LOCAL_TARBALLS_DIR != ""
|
|
yann@265
|
18 |
help
|
|
yann@425
|
19 |
If you say 'y' here, new downloaded tarballs will be saved in the
|
|
yann@265
|
20 |
directory you entered above.
|
|
yann@265
|
21 |
|
|
yann@1
|
22 |
config PREFIX_DIR
|
|
yann@1
|
23 |
string
|
|
yann@1
|
24 |
prompt "Prefix directory"
|
|
yann@1
|
25 |
default "${HOME}/${CT_TARGET}"
|
|
yann@1
|
26 |
help
|
|
yann@1
|
27 |
This is the path the toolchain will run from.
|
|
yann@1
|
28 |
|
|
yann@1
|
29 |
config INSTALL_DIR
|
|
yann@1
|
30 |
string
|
|
yann@1
|
31 |
# prompt "Install directory"
|
|
yann@1
|
32 |
default "${CT_PREFIX_DIR}"
|
|
yann@1
|
33 |
# help
|
|
yann@1
|
34 |
# This is the path the target will be installed into.
|
|
yann@1
|
35 |
#
|
|
yann@1
|
36 |
# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
|
|
yann@1
|
37 |
# you can't write there, you can install somewhere else and have a third
|
|
yann@1
|
38 |
# person do the install for you.
|
|
yann@1
|
39 |
# The reason you might also want to install elsewhere is if you are going
|
|
yann@1
|
40 |
# to package your shinny new toolchain for distribution.
|
|
yann@1
|
41 |
|
|
yann@1
|
42 |
config CUSTOM_PATCH
|
|
yann@1
|
43 |
bool
|
|
yann@1
|
44 |
prompt "Use custom patch directory"
|
|
yann@1
|
45 |
default n
|
|
yann@1
|
46 |
help
|
|
yann@1
|
47 |
If you have custom patches that you want to be applied, say 'Y' here and
|
|
yann@1
|
48 |
enter the path directory below.
|
|
yann@1
|
49 |
|
|
yann@1
|
50 |
Note that you must ensure that the patch directory is arranged the same
|
|
yann@1
|
51 |
way the official directory is.
|
|
yann@1
|
52 |
|
|
yann@1
|
53 |
config CUSTOM_PATCH_ONLY
|
|
yann@1
|
54 |
bool
|
|
yann@1
|
55 |
prompt "Only use custom patches"
|
|
yann@1
|
56 |
default n
|
|
yann@1
|
57 |
depends on CUSTOM_PATCH
|
|
yann@1
|
58 |
help
|
|
yann@197
|
59 |
Don't apply patches coming with crosstool-NG, only those patches available
|
|
yann@197
|
60 |
in the directory below.
|
|
yann@1
|
61 |
|
|
yann@197
|
62 |
If you say 'N' here, then the patches provided with crosstool-NG will be
|
|
yann@197
|
63 |
applied first, and then your patches.
|
|
yann@1
|
64 |
|
|
yann@1
|
65 |
config CUSTOM_PATCH_DIR
|
|
yann@1
|
66 |
string
|
|
yann@1
|
67 |
prompt "Custom patch directory"
|
|
yann@1
|
68 |
default ""
|
|
yann@1
|
69 |
depends on CUSTOM_PATCH
|
|
yann@1
|
70 |
help
|
|
yann@1
|
71 |
Enter the custom patch directory here.
|
|
yann@1
|
72 |
|
|
yann@14
|
73 |
config REMOVE_DOCS
|
|
yann@14
|
74 |
bool
|
|
yann@14
|
75 |
prompt "Remove documentation"
|
|
yann@14
|
76 |
default n
|
|
yann@14
|
77 |
help
|
|
yann@14
|
78 |
Remove the installed documentation (man and info pages).
|
|
yann@14
|
79 |
Gains around 8MiB for a uClibc-based, C and C++ compiler.
|
|
yann@14
|
80 |
|
|
yann@174
|
81 |
config INSTALL_DIR_RO
|
|
yann@174
|
82 |
bool
|
|
yann@174
|
83 |
prompt "Render the toolchain read-only"
|
|
yann@174
|
84 |
default n
|
|
yann@174
|
85 |
help
|
|
yann@174
|
86 |
Render the directory of the toolchain (and its sub-directories)
|
|
yann@174
|
87 |
read-only.
|
|
yann@174
|
88 |
|
|
yann@174
|
89 |
Usefull for toolchains destined for production.
|