# HG changeset patch
# User Bryan Hundven <bryanhundven@gmail.com>
# Date 1291917277 -3600
# Node ID b268256e4a08715d3d37f512318600fc9ef71fb6
# Parent  2b5f5173daa0544deb94c1d8fa519d1431f43b78
config: add option to build statically linked toolchain

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>

diff -r 2b5f5173daa0 -r b268256e4a08 config/toolchain.in
--- a/config/toolchain.in	Mon Nov 29 00:50:21 2010 +0100
+++ b/config/toolchain.in	Thu Dec 09 18:54:37 2010 +0100
@@ -28,6 +28,23 @@
       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