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!!!"
21 gcc 4.3.0 and above requires GMP to build some frontends, and some
22 other components can use them as well.
24 This will be automatically selected if you choose gcc>=4.3.0, but you
25 can say 'Y' here if you want to build this library for the other
26 components (that don't select them by default).
28 The packages that can use GMP and MPFR are:
38 gcc 4.3.0 and above requires MPFR to build some frontends, and some
39 other components can use them as well.
41 This will be automatically selected if you choose gcc>=4.3.0, but you
42 can say 'Y' here if you want to build this library for the other
43 components (that don't select them by default).
45 The packages that can use GMP and MPFR are:
56 gcc-4.4.0 and above requires PPL to build some parts of the optimiser
57 (the GRAPHITE loop optimisation, to be precise).
59 This will be automatically selected if you choose gcc>=4.4.0, but you
60 can say 'Y' here, although it is unknown yet if any other component
70 gcc-4.4.0 and above requires CLooG/PPL to build some parts of the
71 optimiser (the GRAPHITE loop optimisation, to be precise).
73 This will be automatically selected if you choose gcc>=4.4.0, but you
74 can say 'Y' here, although it is unknown yet if any other component
85 gcc-4.4.0 and above can also optionally use MPC to enable additional
86 optimisations on complex numbers. Although MPC is optional,
87 crosstool-NG requires it and uses it to build gcc >= 4.4.0.
89 This will be automatically selected if you choose gcc>=4.4.0, but you
90 can say 'Y' here, although it is unknown yet if any other component
97 gcc-4.5.0 and above can also use libelf to enable some optimisation
98 (LTO, Link-Time Optimisation, to be precise). Although libelf is
99 optional, crosstool-NG requires it and uses it to build gcc >= 4.5.0.
101 This will be automatically selected if you choose gcc>=4.5.0, but you
102 can say 'Y' here, although it is unknown yet if any other component
134 comment "GMP version needed to build for target"
136 source "config/companion_libs/gmp.in"
138 if MPFR || MPFR_TARGET
139 comment "MPFR version needed to build for target"
141 source "config/companion_libs/mpfr.in"
144 comment "PPL version needed to build for target"
146 source "config/companion_libs/ppl.in"
148 if CLOOG || CLOOG_TARGET
149 comment "CLOOG version needed to build for target"
151 source "config/companion_libs/cloog.in"
154 comment "MPC version needed to build for target"
156 source "config/companion_libs/mpc.in"
158 if LIBELF || LIBELF_TARGET
159 comment "libelf version needed to build for target"
161 source "config/companion_libs/libelf.in"
169 comment "Companion libraries common options"
171 config COMPLIBS_CHECK
173 prompt "Check the companion libraries builds (!!! READ HELP!!!)"
176 It is highly recommended to check the newly built companion libraries.
177 Unfortunately, this is a very intensive task, and takes a loooong time.
179 Checking the newly built companion libraries is thus disabled by default,
180 but it is suggested that you check them at least once on your machine,
181 and if they work, disable the check on subsequent builds.
183 If you suspect that one (or more) of your companion libraries is the
184 cause for incorrectly generated code, you should answer 'Y' here.
185 Note however that this will take a really long time. For example,
186 building PPL on my machine takes roughly 1'40", while checking it takes
189 config COMPLIBS_SHARED
191 prompt "Build shared companion libraries"
194 select WRAPPER_NEEDED
196 By default, the companion libraries will be build static. If you want to
197 build shared libraries, then you can say 'Y' here, but a wrapper will be
198 needed (see docs/overview.txt,section "Tools wrapper").
200 It is highly recommended that you keep static libraries.
204 prompt "| Install tools wrapper as:"
205 depends on WRAPPER_NEEDED
206 default TOOLS_WRAPPER_SHELL
208 config TOOLS_WRAPPER_SCRIPT
210 prompt "shell script"
212 If your host has a shell, then you should say 'Y' here, to use
213 a (very very simple) shell script as wrapper.
215 See docs/overview.txt, section "Tools wrapper".
217 config TOOLS_WRAPPER_EXEC
221 If your host lacks a shell, then you should say 'Y' here, to use
224 See docs/overview.txt, section "Tools wrapper".
230 default "script" if TOOLS_WRAPPER_SCRIPT
231 default "exec" if TOOLS_WRAPPER_EXEC