From 264207aa10c17f3cb05d9abeac658a55096427bc Mon Sep 17 00:00:00 2001
From: "Bryan Hundven\"" <bryanhundven@gmail.com>
Date: Thu, 9 Dec 2010 18:54:37 +0100
Subject: 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 --git a/config/toolchain.in b/config/toolchain.in
index 896ccca..12e2b73 100644
--- a/config/toolchain.in
+++ b/config/toolchain.in
@@ -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
-- 
cgit v0.10.2-6-g49f6