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"
16 gcc 4.3.0 and above requires both GMP and MPFR to build some frontends,
17 and some other components can use them as well.
19 These will be automatically selected if you choose gcc>=4.3.0, but you
20 can say 'Y' here if you want to build those two libraries for the other
21 components (that don't select them by default).
23 The packages that can use GMP and MPFR are:
29 source config/companion_libs/gmp.in
30 source config/companion_libs/mpfr.in
35 prompt "PPL, GLooG/PPL and MPC"
39 gcc-4.4.0 and above requires PPL and CLooG/PPL to build some parts
40 of the optimiser (GRAPHITE loop optimisation, to be precise).
42 In addition to those, gcc-4.4 also optionally uses MPC to enable
43 additional optimisations on complex numbers. Although MPC is optional,
44 crosstool-NG requires it and uses it to build gcc >= 4.4.0.
46 These will be automatically selected if you choose gcc>=4.4.0, but you
47 can say 'Y' here, although it is unknown yet if any other component
51 source config/companion_libs/ppl.in
52 source config/companion_libs/cloog.in
53 source config/companion_libs/mpc.in
59 comment "Companion libraries common options"
60 depends on GMP_MPFR || PPL_CLOOG_MPC
62 config COMP_LIBS_CHECK
64 prompt "| Check the companion libraries builds (!!! READ HELP!!!)"
65 depends on GMP_MPFR || PPL_CLOOG_MPC
68 It is highly recommended to check the newly built companion libraries.
69 Unfortunately, this is a very intensive task, and takes a loooong time.
71 Checking the newly built companion libraries is thus disabled by default,
72 but it is suggested that you check them at least once on your machine,
73 and if they work, disable the check on subsequent builds.
75 If you suspect that one (or more) of your companion libraries is the
76 cause for incorrectly generated code, you should answer 'Y' here.
77 Note however that this will take a really long time. For example,
78 building PPL on my machine takes roughly 1'40", while checking it takes
81 config COMP_LIBS_TARGET
83 prompt "| Build companion libraries for the target"
84 depends on GMP_MPFR || PPL_CLOOG_MPC
85 depends on ! BARE_METAL
88 Also build companion libraries for the target. This can be usefull if
89 you want to later build a compiler that will run on the target, or if
90 you want to run gdb natively on the target.
92 Please note that for now, crosstool-NG can only build GMP and MPFR so.
96 prompt "| Install tools wrapper as:"
97 depends on WRAPPER_NEEDED
98 default TOOLS_WRAPPER_SHELL
100 config TOOLS_WRAPPER_SCRIPT
102 prompt "shell script"
104 If your host has a shell, then you should say 'Y' here, to use
105 a (very very simple) shell script as wrapper.
107 See docs/overview.txt, section "Tools wrapper".
109 config TOOLS_WRAPPER_EXEC
113 If your host lacks a shell, then you should say 'Y' here, to use
116 See docs/overview.txt, section "Tools wrapper".
122 default "script" if TOOLS_WRAPPER_SCRIPT
123 default "exec" if TOOLS_WRAPPER_EXEC