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!!!"
55 source "config/companion_libs/gmp.in"
58 source "config/companion_libs/mpfr.in"
61 source "config/companion_libs/ppl.in"
64 source "config/companion_libs/cloog.in"
67 source "config/companion_libs/mpc.in"
69 if LIBELF || LIBELF_TARGET
70 comment "libelf version needed to build for target"
72 source "config/companion_libs/libelf.in"
80 comment "Companion libraries common options"
84 prompt "Check the companion libraries builds (!!! READ HELP!!!)"
87 It is highly recommended to check the newly built companion libraries.
88 Unfortunately, this is a very intensive task, and takes a loooong time.
90 Checking the newly built companion libraries is thus disabled by default,
91 but it is suggested that you check them at least once on your machine,
92 and if they work, disable the check on subsequent builds.
94 If you suspect that one (or more) of your companion libraries is the
95 cause for incorrectly generated code, you should answer 'Y' here.
96 Note however that this will take a really long time. For example,
97 building PPL on my machine takes roughly 1'40", while checking it takes
100 config COMPLIBS_SHARED
102 prompt "Build shared companion libraries"
105 select WRAPPER_NEEDED
107 By default, the companion libraries will be build static. If you want to
108 build shared libraries, then you can say 'Y' here, but a wrapper will be
109 needed (see docs/overview.txt,section "Tools wrapper").
111 It is highly recommended that you keep static libraries.
115 prompt "| Install tools wrapper as:"
116 depends on WRAPPER_NEEDED
117 default TOOLS_WRAPPER_SHELL
119 config TOOLS_WRAPPER_SCRIPT
121 prompt "shell script"
123 If your host has a shell, then you should say 'Y' here, to use
124 a (very very simple) shell script as wrapper.
126 See docs/overview.txt, section "Tools wrapper".
128 config TOOLS_WRAPPER_EXEC
132 If your host lacks a shell, then you should say 'Y' here, to use
135 See docs/overview.txt, section "Tools wrapper".
141 default "script" if TOOLS_WRAPPER_SCRIPT
142 default "exec" if TOOLS_WRAPPER_EXEC