yann@693
|
1 |
# Options specific to extracting packages
|
yann@693
|
2 |
|
yann@693
|
3 |
comment "Extracting"
|
yann@693
|
4 |
|
yann@693
|
5 |
config FORCE_EXTRACT
|
yann@693
|
6 |
bool
|
yann@693
|
7 |
prompt "Force extractions"
|
yann@693
|
8 |
default n
|
yann@693
|
9 |
help
|
yann@693
|
10 |
Force extraction of already exctracted tarballs.
|
yann@693
|
11 |
|
yann@693
|
12 |
Usefull if you suspect a previous extract did not complete (eg. broken
|
yann@693
|
13 |
tarball), or you added a new set of patches for this component.
|
yann@693
|
14 |
|
yann@693
|
15 |
config OVERIDE_CONFIG_GUESS_SUB
|
yann@693
|
16 |
bool
|
yann@693
|
17 |
prompt "Override config.{guess,sub}"
|
yann@693
|
18 |
default y
|
yann@693
|
19 |
help
|
yann@693
|
20 |
Override tools' versions of config.guess and config.sub with the ones
|
yann@693
|
21 |
from crosstool-NG. This means that all instances of config.guess and
|
yann@693
|
22 |
config.sub in gcc, binutils, glibc, etc... will be replaced.
|
yann@693
|
23 |
|
yann@693
|
24 |
Most of the time, the versions of those scripts found in packages are old
|
yann@693
|
25 |
versions, thus lacking some target definitions. This is the case for
|
yann@693
|
26 |
uClibc-based tuples in old versions of gcc and gdb, for example.
|
yann@693
|
27 |
|
yann@693
|
28 |
Also, doing so will guarantee that all components have the same tuples
|
yann@693
|
29 |
definitions for your target, and not diverging ones.
|
yann@693
|
30 |
|
yann@693
|
31 |
You can update the ones provided with crosstool-NG by first running:
|
yann@693
|
32 |
ct-ng updatetools
|
yann@693
|
33 |
in the directory where you want to run crosstool-NG prior to the build.
|
yann@693
|
34 |
|
yann@693
|
35 |
config ONLY_EXTRACT
|
yann@693
|
36 |
bool
|
yann@693
|
37 |
prompt "Stop after extracting tarballs"
|
yann@693
|
38 |
default n
|
yann@693
|
39 |
help
|
yann@693
|
40 |
Exit after unpacking and patching tarballs.
|
yann@693
|
41 |
|
yann@693
|
42 |
Usefull to look at the code before doing the build itself.
|
yann@1510
|
43 |
|
yann@1510
|
44 |
choice
|
yann@1510
|
45 |
prompt "Patches origin"
|
yann@1510
|
46 |
bool
|
yann@1510
|
47 |
default PATCH_BUNDLED
|
yann@1510
|
48 |
|
yann@1510
|
49 |
config PATCH_BUNDLED
|
yann@1510
|
50 |
bool
|
yann@1510
|
51 |
prompt "Bundled only"
|
yann@1510
|
52 |
help
|
yann@1510
|
53 |
Only apply patches bundled with crosstool-NG.
|
yann@1510
|
54 |
|
yann@1510
|
55 |
config PATCH_LOCAL
|
yann@1510
|
56 |
bool
|
yann@1510
|
57 |
prompt "Local only"
|
yann@1510
|
58 |
select PATCH_USE_LOCAL
|
yann@1510
|
59 |
help
|
yann@1510
|
60 |
Only apply your local patches.
|
yann@1510
|
61 |
|
yann@1510
|
62 |
config PATCH_BUNDLED_LOCAL
|
yann@1510
|
63 |
bool
|
yann@1510
|
64 |
prompt "Bundled, then local"
|
yann@1510
|
65 |
select PATCH_USE_LOCAL
|
yann@1510
|
66 |
help
|
yann@1510
|
67 |
Apply the patches bundled with crosstool-NG,
|
yann@1510
|
68 |
then apply your local patches.
|
yann@1510
|
69 |
|
yann@1510
|
70 |
config PATCH_LOCAL_BUNDLED
|
yann@1510
|
71 |
bool
|
yann@1510
|
72 |
prompt "Local, then bundled"
|
yann@1510
|
73 |
select PATCH_USE_LOCAL
|
yann@1510
|
74 |
help
|
yann@1510
|
75 |
Apply your local patches, then apply the patches
|
yann@1510
|
76 |
bundled with crosstool-NG.
|
yann@1510
|
77 |
|
yann@1510
|
78 |
config PATCH_BUNDLED_FALLBACK_LOCAL
|
yann@1510
|
79 |
bool
|
yann@1510
|
80 |
prompt "Bundled only, local if no bundled"
|
yann@1510
|
81 |
select PATCH_USE_LOCAL
|
yann@1510
|
82 |
select PATCH_SINGLE
|
yann@1510
|
83 |
help
|
yann@1510
|
84 |
Apply the patches bundled with crosstool-NG;
|
yann@1510
|
85 |
if there's no bundled patches, apply your local patches.
|
yann@1510
|
86 |
|
yann@1510
|
87 |
config PATCH_LOCAL_FALLBACK_BUNDLED
|
yann@1510
|
88 |
bool
|
yann@1510
|
89 |
prompt "Local only, bundled if no local"
|
yann@1510
|
90 |
select PATCH_USE_LOCAL
|
yann@1510
|
91 |
select PATCH_SINGLE
|
yann@1510
|
92 |
help
|
yann@1510
|
93 |
Only apply your local patches;
|
yann@1510
|
94 |
if there's no local patches, apply patches bundled with crosstool-NG.
|
yann@1510
|
95 |
|
yann@1630
|
96 |
config PATCH_NONE
|
yann@1630
|
97 |
bool
|
yann@1630
|
98 |
prompt "None"
|
yann@1630
|
99 |
help
|
yann@1630
|
100 |
Don't use any patch at all.
|
yann@1630
|
101 |
|
yann@1630
|
102 |
Please be carefull if you select this. Most components do require
|
yann@1630
|
103 |
patches to properly build. It can happen, however, that support for
|
yann@1630
|
104 |
your architecture is clean enough that you can build a toolchain
|
yann@1630
|
105 |
with no patch. But most probably, this is *not* the case.
|
yann@1630
|
106 |
|
yann@1630
|
107 |
Be safe, use (the bundeld) patches.
|
yann@1630
|
108 |
|
yann@1510
|
109 |
endchoice
|
yann@1510
|
110 |
|
yann@1510
|
111 |
config PATCH_ORDER
|
yann@1510
|
112 |
string
|
yann@1510
|
113 |
default "bundled" if PATCH_BUNDLED
|
yann@1510
|
114 |
default "local" if PATCH_LOCAL
|
yann@1510
|
115 |
default "bundled,local" if PATCH_BUNDLED_LOCAL
|
yann@1510
|
116 |
default "local,bundled" if PATCH_LOCAL_BUNDLED
|
yann@1630
|
117 |
default "none" if PATCH_NONE
|
yann@1510
|
118 |
|
yann@1510
|
119 |
config PATCH_SINGLE
|
yann@1510
|
120 |
bool
|
yann@1510
|
121 |
default n
|
yann@1510
|
122 |
|
yann@1510
|
123 |
config PATCH_USE_LOCAL
|
yann@1510
|
124 |
bool
|
yann@1510
|
125 |
default n
|
yann@1510
|
126 |
|
yann@1510
|
127 |
config LOCAL_PATCH_DIR
|
yann@1510
|
128 |
string
|
yann@1510
|
129 |
prompt "| Local patch directory"
|
yann@1510
|
130 |
default ""
|
yann@1510
|
131 |
depends on PATCH_USE_LOCAL
|
yann@1510
|
132 |
help
|
yann@1510
|
133 |
Enter the custom patch directory here.
|
yann@1510
|
134 |
|
yann@1510
|
135 |
Note that you must ensure that the directory contianing your custom
|
yann@1510
|
136 |
patches is arranged the same way the official directory is.
|