1 # Companion libraries config options
2 # Those libraries are required for different versions of gcc,
3 # and can be used by binutils and gdb (maybe others as well).
5 menu "Companion libraries"
7 comment "FIXME: check real dependencies!!!"
23 gcc 4.3.0 and above requires GMP to build some frontends, and some
24 other components can use them as well.
26 This will be automatically selected if you choose gcc>=4.3.0, but you
27 can say 'Y' here if you want to build this library for the other
28 components (that don't select them by default).
30 The packages that can use GMP and MPFR are:
42 gcc 4.3.0 and above requires MPFR to build some frontends, and some
43 other components can use them as well.
45 This will be automatically selected if you choose gcc>=4.3.0, but you
46 can say 'Y' here if you want to build this library for the other
47 components (that don't select them by default).
49 The packages that can use GMP and MPFR are:
62 gcc-4.4.0 and above requires PPL to build some parts of the optimiser
63 (the GRAPHITE loop optimisation, to be precise).
65 This will be automatically selected if you choose gcc>=4.4.0, but you
66 can say 'Y' here, although it is unknown yet if any other component
78 gcc-4.4.0 and above requires CLooG/PPL to build some parts of the
79 optimiser (the GRAPHITE loop optimisation, to be precise).
81 This will be automatically selected if you choose gcc>=4.4.0, but you
82 can say 'Y' here, although it is unknown yet if any other component
95 gcc-4.4.0 and above can also optionally use MPC to enable additional
96 optimisations on complex numbers. Although MPC is optional,
97 crosstool-NG requires it and uses it to build gcc >= 4.4.0.
99 This will be automatically selected if you choose gcc>=4.4.0, but you
100 can say 'Y' here, although it is unknown yet if any other component
104 source config/companion_libs/gmp.in
107 source config/companion_libs/mpfr.in
110 source config/companion_libs/ppl.in
113 source config/companion_libs/cloog.in
116 source config/companion_libs/mpc.in
122 comment "Companion libraries common options"
123 depends on COMPLIBS || WRAPPER_NEEDED
127 config COMP_LIBS_CHECK
129 prompt "| Check the companion libraries builds (!!! READ HELP!!!)"
132 It is highly recommended to check the newly built companion libraries.
133 Unfortunately, this is a very intensive task, and takes a loooong time.
135 Checking the newly built companion libraries is thus disabled by default,
136 but it is suggested that you check them at least once on your machine,
137 and if they work, disable the check on subsequent builds.
139 If you suspect that one (or more) of your companion libraries is the
140 cause for incorrectly generated code, you should answer 'Y' here.
141 Note however that this will take a really long time. For example,
142 building PPL on my machine takes roughly 1'40", while checking it takes
145 config COMPLIBS_TARGET
147 prompt "| Build companion libraries for the target"
148 depends on ! BARE_METAL
151 Also build companion libraries for the target. This can be usefull if
152 you want to later build a compiler that will run on the target, or if
153 you want to run gdb natively on the target.
155 Please note that for now, crosstool-NG can only build GMP and MPFR so.
161 prompt "| Install tools wrapper as:"
162 depends on WRAPPER_NEEDED
163 default TOOLS_WRAPPER_SHELL
165 config TOOLS_WRAPPER_SCRIPT
167 prompt "shell script"
169 If your host has a shell, then you should say 'Y' here, to use
170 a (very very simple) shell script as wrapper.
172 See docs/overview.txt, section "Tools wrapper".
174 config TOOLS_WRAPPER_EXEC
178 If your host lacks a shell, then you should say 'Y' here, to use
181 See docs/overview.txt, section "Tools wrapper".
187 default "script" if TOOLS_WRAPPER_SCRIPT
188 default "exec" if TOOLS_WRAPPER_EXEC