gitolite/buildrootschalter
gitolite
/
buildrootschalter
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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 <abrodkin@synopsys.com>

Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
Cc: Peter Korsgaard <peter@korsgaard.com>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
Alexey Brodkin 2014-10-12 18:34:44 +02:00 committed by Peter Korsgaard
parent 1dbdf1e2a2
commit 7d9c0df074
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Config.in
View File

@ -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"