aboutsummaryrefslogtreecommitdiff
path: root/Config.in
diff options
context:
space:
mode:
authorGravatar Denis Vlasenko <vda.linux@googlemail.com>2007-10-07 17:06:26 +0000
committerGravatar Denis Vlasenko <vda.linux@googlemail.com>2007-10-07 17:06:26 +0000
commitf545be083d3e9758b70edf16aa532528cd7ce108 (patch)
tree136f8792a5217e6558a29aee33eef199e338f652 /Config.in
parentdef88985966a9351911844d42e06b735977bcb72 (diff)
downloadbusybox-f545be083d3e9758b70edf16aa532528cd7ce108.tar.gz
busybox-f545be083d3e9758b70edf16aa532528cd7ce108.tar.bz2
reviving libbusybox, adding CONFIG_INDIVIDUAL part 4
Diffstat (limited to 'Config.in')
-rw-r--r--Config.in46
1 files changed, 33 insertions, 13 deletions
diff --git a/Config.in b/Config.in
index 64281f03e..b046812c7 100644
--- a/Config.in
+++ b/Config.in
@@ -311,24 +311,32 @@ config BUILD_LIBBUSYBOX
###
### Say 'N' if in doubt.
+config FEATURE_INDIVIDUAL
+ bool "Produce a binary for each applet, linked against libbusybox"
+ default y
+ depends on !STATIC && BUILD_LIBBUSYBOX
+ help
+ If your CPU architecture doesn't allow for sharing text/rodata
+ sections of running binaries, but allows for runtime dynamic
+ libraries, this option will allow you to reduce memory footprint
+ when you have many different applets running at once.
+
+ If your CPU architecture allows for sharing text/rodata,
+ having single binary is more optimal.
+
+ Each applet will be a tiny program, dynamically linked
+ against libbusybox.so.N.N.N.
+
+ You need to have a working dynamic linker.
+
config FEATURE_SHARED_BUSYBOX
bool "Produce additional busybox binary linked against libbusybox"
- default y if BUILD_LIBBUSYBOX
+ default y
depends on !STATIC && BUILD_LIBBUSYBOX
help
- You need to have a working dynamic linker to use this variant.
+ Build busybox, dynamically linked against libbusybox.so.N.N.N.
-config LFS
- bool "Build with Large File Support (for accessing files > 2 GB)"
- default n
- select FDISK_SUPPORT_LARGE_DISKS
- help
- If you want to build BusyBox with large file support, then enable
- this option. This will have no effect if your kernel or your C
- library lacks large file support for large files. Some of the
- programs that can benefit from large file support include dd, gzip,
- cp, mount, tar, and many others. If you want to access files larger
- than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
+ You need to have a working dynamic linker.
### config BUILD_AT_ONCE
### bool "Compile all sources at once"
@@ -349,6 +357,18 @@ config LFS
###
### Say 'N' unless you know what you are doing.
+config LFS
+ bool "Build with Large File Support (for accessing files > 2 GB)"
+ default n
+ select FDISK_SUPPORT_LARGE_DISKS
+ help
+ If you want to build BusyBox with large file support, then enable
+ this option. This will have no effect if your kernel or your C
+ library lacks large file support for large files. Some of the
+ programs that can benefit from large file support include dd, gzip,
+ cp, mount, tar, and many others. If you want to access files larger
+ than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
+
endmenu
menu 'Debugging Options'