From 7d9c0df074ef412fe5012ad6e2b4d96e04c95859 Mon Sep 17 00:00:00 2001 From: Alexey Brodkin Date: Sun, 12 Oct 2014 18:34:44 +0200 Subject: [PATCH] Config.in: update description of BR2_PREFER_STATIC_LIB With time BR2_PREFER_STATIC_LIB option meaning changed from "prefer static libs when possible" to "do not build dynamic libs and build statically linked applications". This patch changes the option description. Note that variable name is kept unchanged on purpose - it will be modified later when real "prefer static" mode will be introduced. [Peter: tweak help text as suggested by Thomas and Yann] Signed-off-by: Alexey Brodkin Cc: Thomas Petazzoni Cc: Gustavo Zacarias Cc: Peter Korsgaard Acked-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard --- Config.in | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/Config.in b/Config.in index 24aa883111..9cefcbce5d 100644 --- a/Config.in +++ b/Config.in @@ -536,15 +536,19 @@ comment "enabling Stack Smashing Protection requires support in the toolchain" depends on !BR2_TOOLCHAIN_HAS_SSP config BR2_PREFER_STATIC_LIB - bool "prefer static libraries" + bool "build statically linked applications, no dynamic libraries" help - Where possible, build and use static libraries for the target. - This potentially increases your code size and should only be + Build all applications for the target statically linked. + This potentially increases your filesystem size and should only be used if you know what you do. - The default is to build dynamic libraries and use those on - the target filesystem. - WARNING: This is highly experimental at the moment. + Note that some applications cannot be build statically and so are + intentionally disabled. + + The default (if this option is disabled) is to build dynamic + libraries and dynamically link applications to use those on the + target filesystem. + config BR2_PACKAGE_OVERRIDE_FILE string "location of a package override file"