ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-19 04:47:52 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

config: add option to build statically linked toolchain

Browse Source 
Add a config option to statically build the host tools.
Impacted tools can use that option to decide wether to build
statically or shared.

For now, no tool uses it, but they'll be added one at a time
in the next commits.

Signed-off-by: "Bryan Hundven" <bryanhundven@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
This commit is contained in:
Bryan Hundven" 2010-12-09 18:54:37 +01:00 committed by Bryan Hundven
parent 63750f8841
commit 264207aa10
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
config/toolchain.in
View File

@ -28,6 +28,23 @@ config SYSROOT_DIR_PREFIX
In fact, the sysroot path is constructed as:
${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/sys-root
config STATIC_TOOLCHAIN
bool
prompt "Build Static Toolchain (EXPERIMENTAL)"
depends on EXPERIMENTAL
default n
help
Build static host binaries.
If you wish to move the toolchain to another host, and you are not
confident that this host has the required versions of system libs, then
you can say 'Y' here, and all the host tools will be linked staticaly.
The default is 'N', to build dynamicaly-linked host binaries.
NOTE: this has no connection to whether the target libraries will be
dynamic or static. This only applies to the tools themselves.
comment "Tuple completion and aliasing"
config TARGET_VENDOR