complibs/ppl: remove unnecessary (and confusing) --enable-cxx configure switch.
PPL does not use the "--enable-cxx" configure switch at all; it's
possibly a cut-and-paste leftover from 'gmp.sh'. (PPL is written in C++
natively, so it doesn't make much sense to have to enable C++; GMP, on
the other hand, is written in C with an optional C++ wrapper.)
Signed-Off-By: Anthony Foiani <anthony.foiani@gmail.com>
1 # Options related to paths and install
5 config LOCAL_TARBALLS_DIR
7 prompt "Local tarballs directory" if ! BACKEND
10 If you have previously downloaded the tarballs, enter the PATH where
15 prompt "Save new tarballs" if ! BACKEND
16 depends on LOCAL_TARBALLS_DIR != "" || BACKEND
18 default n if ! BACKEND
20 If you say 'y' here, new downloaded tarballs will be saved in the
21 directory you entered above.
25 prompt "Working directory" if ! BACKEND
26 default "${CT_TOP_DIR}/.build"
28 Set this to the directory where all build actions will be done.
30 The default is "${CT_TOP_DIR}/.build", and leaving this option
31 empty will also use the default.
33 You should not need to change that, except in one very peculiar
35 - your crosstool-NG source directory is on the network
36 - you configured crosstool-NG with --local
37 This kind of setup is a pain, as any action involving source file
38 access would have to go through the wire. In this case, you should
39 set CT_WORK_DIR to point to a path local to your machine, to avoid
42 Do *NOT* change it if you don't know better.
46 prompt "Prefix directory" if ! BACKEND
47 default "${HOME}/x-tools/${CT_TARGET}"
49 This is the path the toolchain will run from.
53 # prompt "Install directory"
54 default "${CT_PREFIX_DIR}"
56 # This is the path the toolchain will be installed into.
58 # Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
59 # you can't write there, you can install somewhere else and have a third
60 # person do the install for you.
61 # The reason you might also want to install elsewhere is if you are going
62 # to package your shinny new toolchain for distribution.
64 config RM_RF_PREFIX_DIR
66 prompt "| Remove the prefix dir prior to building"
70 If you say 'y' here, then PREFIX_DIR (above) will be eradicated
71 prior to the toolchain is built.
73 This can be usefull when you are trying different settings (due
74 to build failures or feature tests). In this case, to avoid using
75 a potentially broken previous toolchain, the install location is
76 removed, to start afresh.
78 On the oher hand, if you are building a final toolchain, and install
79 it into a directory with pre-install, unrelated programs, it would be
80 damageable to remove that directory. In this case, you may want to
83 Note that when acting as a backend, this option is not available, and
88 prompt "Remove documentation"
91 Remove the installed documentation (man and info pages).
92 Gains around 8MiB for a uClibc-based, C and C++ compiler.
96 prompt "Render the toolchain read-only"
99 Render the directory of the toolchain (and its sub-directories)
102 Usefull for toolchains destined for production.
104 config STRIP_ALL_TOOLCHAIN_EXECUTABLES
106 prompt "Strip all toolchain executables"
109 All build host executables contain a lot of unnecessary info.
110 By stripping all executables it slightly speeds up the compilation
112 NOTE: It does NOT strip the target libraries, only HOST executables