package/busybox/config/Config.in

   1 #
   2 # For a description of the syntax of this configuration file,
   3 # see scripts/kbuild/config-language.txt.
   4 #
   5
   6
   7 config BUSYBOX_HAVE_DOT_CONFIG
   8         bool
   9         default y
  10
  11 menu "Busybox Settings"
  12
  13 menu "General Configuration"
  14
  15 choice
  16         prompt "Buffer allocation policy"
  17         default BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  18         help
  19           There are 3 ways BusyBox can handle buffer allocations:
  20           - Use malloc. This costs code size for the call to xmalloc.
  21           - Put them on stack. For some very small machines with limited stack
  22             space, this can be deadly.  For most folks, this works just fine.
  23           - Put them in BSS. This works beautifully for computers with a real
  24             MMU (and OS support), but wastes runtime RAM for uCLinux. This
  25             behavior was the only one available for BusyBox versions 0.48 and
  26             earlier.
  27
  28 config BUSYBOX_CONFIG_FEATURE_BUFFERS_USE_MALLOC
  29         bool "Allocate with Malloc"
  30
  31 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  32         bool "Allocate on the Stack"
  33
  34 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_IN_BSS
  35         bool "Allocate in the .bss section"
  36
  37 endchoice
  38
  39 config BUSYBOX_CONFIG_FEATURE_VERBOSE_USAGE
  40         bool "Show verbose applet usage messages"
  41         default y
  42         help
  43           All BusyBox applets will show more verbose help messages when
  44           busybox is invoked with --help.  This will add a lot of text to the
  45           busybox binary.  In the default configuration, this will add about
  46           13k, but it can add much more depending on your configuration.
  47
  48 config BUSYBOX_CONFIG_FEATURE_INSTALLER
  49         bool "Support --install [-s] to install applet links at runtime"
  50         default n
  51         help
  52           Enable 'busybox --install [-s]' support.  This will allow you to use
  53           busybox at runtime to create hard links or symlinks for all the
  54           applets that are compiled into busybox.  This feature requires the
  55           /proc filesystem.
  56
  57 config BUSYBOX_CONFIG_LOCALE_SUPPORT
  58         bool "Enable locale support (system needs locale for this to work)"
  59         default n
  60         help
  61           Enable this if your system has locale support and you would like
  62           busybox to support locale settings.
  63
  64 config BUSYBOX_CONFIG_FEATURE_DEVFS
  65         bool "Support for devfs"
  66         default y
  67         help
  68           Enable if you want BusyBox to work with devfs.
  69
  70 config BUSYBOX_CONFIG_FEATURE_DEVPTS
  71         bool "Use the devpts filesystem for Unix98 PTYs"
  72         default y if BUSYBOX_CONFIG_FEATURE_DEVFS
  73         help
  74           Enable if you want BusyBox to use Unix98 PTY support. If enabled,
  75           busybox will use /dev/ptmx for the master side of the pseudoterminal
  76           and /dev/pts/<number> for the slave side.  Otherwise, BSD style
  77           /dev/ttyp<number> will be used. To use this option, you should have
  78           devpts or devfs mounted.
  79
  80 config BUSYBOX_CONFIG_FEATURE_CLEAN_UP
  81         bool "Clean up all memory before exiting (usually not needed)"
  82         default n
  83         help
  84           As a size optimization, busybox normally exits without explicitly
  85           freeing dynamically allocated memory or closing files.  This saves
  86           space since the OS will clean up for us, but it can confuse debuggers
  87           like valgrind, which report tons of memory and resource leaks.
  88
  89           Don't enable this unless you have a really good reason to clean
  90           things up manually.
  91
  92 config BUSYBOX_CONFIG_FEATURE_SUID
  93         bool "Support for SUID/SGID handling"
  94         default y
  95         help
  96           Support SUID and SGID binaries.
  97
  98 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
  99         bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
 100         default n if BUSYBOX_CONFIG_FEATURE_SUID
 101         depends on BUSYBOX_CONFIG_FEATURE_SUID
 102         help
 103           Allow the SUID / SGID state of an applet to be determined runtime by
 104           checking /etc/busybox.conf.  The format of this file is as follows:
 105
 106           <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
 107
 108           An example might help:
 109
 110           [SUID]
 111           su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
 112           su = ssx        # exactly the same
 113
 114           mount = sx- root.disk # applet mount can be run by root and members of group disk
 115                                 # and runs with euid=0
 116
 117           cp = --- # disable applet cp for everyone
 118
 119           The file has to be owned by user root, group root and has to be
 120           writeable only by root:
 121                 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
 122           The busybox executable has to be owned by user root, group
 123           root and has to be setuid root for this to work:
 124                 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
 125
 126           Robert 'sandman' Griebl has more information here:
 127           <url: http://www.softforge.de/bb/suid.html >.
 128
 129 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG_QUIET
 130         bool "Suppress warning message if /etc/busybox.conf is not readable"
 131         default n
 132         depends on BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 133         help
 134           /etc/busybox.conf should be readable by the user needing the SUID, check
 135           this option to avoid users to be notified about missing permissions.
 136
 137 config BUSYBOX_CONFIG_SELINUX
 138         bool "Support NSA Security Enhanced Linux"
 139         default n
 140         help
 141           Enable support for SE Linux in applets ls, ps, and id.  Also provide
 142           the option of compiling in SE Linux applets.
 143
 144           If you do not have a complete SE Linux Full Userland installed, this
 145           stuff will not compile.  Go visit
 146                 http://www.nsa.gov/selinux/index.html
 147           to download the necessary stuff to allow busybox to compile with this
 148           option enabled.
 149
 150           Most people will leave this set to 'N'.
 151
 152 endmenu
 153
 154 menu 'Build Options'
 155
 156 config BUSYBOX_CONFIG_STATIC
 157         bool "Build BusyBox as a static binary (no shared libs)"
 158         default n
 159         help
 160           If you want to build a static BusyBox binary, which does not
 161           use or require any shared libraries, then enable this option.
 162           This can cause BusyBox to be considerably larger, so you should
 163           leave this option false unless you have a good reason (i.e.
 164           your target platform does not support shared libraries, or
 165           you are building an initrd which doesn't need anything but
 166           BusyBox, etc).
 167
 168           Most people will leave this set to 'N'.
 169
 170 # The busybox shared library feature is there so make standalone can produce
 171 # smaller applets.  Since make standalone isn't in yet, there's nothing using
 172 # this yet, and so it's disabled.
 173 config BUSYBOX_CONFIG_DISABLE_SHARED
 174         bool
 175         default n
 176
 177 config BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 178         bool "Build shared libbusybox"
 179         default n
 180         depends on BUSYBOX_CONFIG_DISABLE_SHARED
 181         help
 182           Build a shared library libbusybox.so which contains all
 183           libraries used inside busybox.
 184
 185 config BUSYBOX_CONFIG_FEATURE_FULL_LIBBUSYBOX
 186         bool "Feature-complete libbusybox"
 187         default n if !CONFIG_FEATURE_SHARED_BUSYBOX
 188         depends on BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 189         help
 190           Build a libbusybox with the complete feature-set, disregarding
 191           the actually selected config.
 192
 193           Normally, libbusybox will only contain the features which are
 194           used by busybox itself. If you plan to write a separate
 195           standalone application which uses libbusybox say 'Y'.
 196
 197           Note: libbusybox is GPL, not LGPL, and exports no stable API that
 198           might act as a copyright barrier.  We can and will modify the
 199           exported function set between releases (even minor version number
 200           changes), and happily break out-of-tree features.
 201
 202           Say 'N' if in doubt.
 203
 204 config BUSYBOX_CONFIG_FEATURE_SHARED_BUSYBOX
 205         bool "Use shared libbusybox for busybox"
 206         default n if BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 207         depends on !CONFIG_STATIC && BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 208         help
 209           Use libbusybox.so also for busybox itself.
 210           You need to have a working dynamic linker to use this variant.
 211
 212 config BUSYBOX_CONFIG_LFS
 213         bool
 214         default y
 215         select BUSYBOX_FDISK_SUPPORT_LARGE_DISKS
 216         help
 217           If you want to build BusyBox with large file support, then enable
 218           this option.  This will have no effect if your kernel or your C
 219           library lacks large file support for large files.  Some of the
 220           programs that can benefit from large file support include dd, gzip,
 221           cp, mount, tar, and many others.  If you want to access files larger
 222           than 2 Gigabytes, enable this option.  Otherwise, leave it set to 'N'.
 223
 224 config BUSYBOX_USING_CROSS_COMPILER
 225         bool
 226         default y
 227         help
 228           Do you want to build BusyBox with a Cross Compiler?  If so,
 229           then enable this option.  Otherwise leave it set to 'N'.
 230
 231 config BUSYBOX_CROSS_COMPILER_PREFIX
 232         string
 233         default "mipsel-uclibc-"
 234         depends on BUSYBOX_USING_CROSS_COMPILER
 235         help
 236           If you want to build BusyBox with a cross compiler, then you
 237           will need to set this to the cross-compiler prefix.  For example,
 238           if my cross-compiler is /usr/i386-linux-uclibc/bin/i386-uclibc-gcc
 239           then I would enter '/usr/i386-linux-uclibc/bin/i386-uclibc-' here,
 240           which will ensure the correct compiler is used.
 241
 242 config BUSYBOX_EXTRA_CFLAGS_OPTIONS
 243         string
 244         default "-Os "
 245         help
 246           Do you want to pass any extra CFLAGS options to the compiler as
 247           you build BusyBox? If so, this is the option for you...  For example,
 248           if you want to add some simple compiler switches (like -march=i686),
 249           or check for warnings using -Werror, just those options here.
 250
 251 config BUSYBOX_CONFIG_BUILD_AT_ONCE
 252         bool "Compile all sources at once"
 253         default n
 254         help
 255           Normally each source-file is compiled with one invocation of
 256           the compiler.
 257           If you set this option, all sources are compiled at once.
 258           This gives the compiler more opportunities to optimize which can
 259           result in smaller and/or faster binaries.
 260
 261           Setting this option will consume alot of memory, e.g. if you
 262           enable all applets with all features, gcc uses more than 300MB
 263           RAM during compilation of busybox.
 264
 265           This option is most likely only beneficial for newer compilers
 266           such as gcc-4.1 and above.
 267
 268           Say 'N' unless you know what you are doing.
 269
 270 endmenu
 271
 272 menu 'Debugging Options'
 273
 274 config BUSYBOX_CONFIG_DEBUG
 275         bool "Build BusyBox with Debugging symbols"
 276         default n
 277         help
 278           Say Y here if you wish to compile BusyBox with debugging symbols.
 279           This will allow you to use a debugger to examine BusyBox internals
 280           while applets are running.  This increases the size of the binary
 281           considerably and should only be used when doing development.
 282           If you are doing development and want to debug BusyBox, answer Y.
 283
 284           Most people should answer N.
 285
 286 choice
 287         prompt "Additional debugging library"
 288         default BUSYBOX_CONFIG_NO_DEBUG_LIB
 289         depends on BUSYBOX_CONFIG_DEBUG
 290         help
 291           Using an additional debugging library will make BusyBox become
 292           considerable larger and will cause it to run more slowly.  You
 293           should always leave this option disabled for production use.
 294
 295           dmalloc support:
 296           ----------------
 297           This enables compiling with dmalloc ( http://dmalloc.com/ )
 298           which is an excellent public domain mem leak and malloc problem
 299           detector.  To enable dmalloc, before running busybox you will
 300           want to properly set your environment, for example:
 301             export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
 302           The 'debug=' value is generated using the following command
 303             dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
 304                -p check-fence -p check-heap -p check-lists -p check-blank \
 305                -p check-funcs -p realloc-copy -p allow-free-null
 306
 307           Electric-fence support:
 308           -----------------------
 309           This enables compiling with Electric-fence support.  Electric
 310           fence is another very useful malloc debugging library which uses
 311           your computer's virtual memory hardware to detect illegal memory
 312           accesses.  This support will make BusyBox be considerable larger
 313           and run slower, so you should leave this option disabled unless
 314           you are hunting a hard to find memory problem.
 315
 316
 317 config BUSYBOX_CONFIG_NO_DEBUG_LIB
 318         bool "None"
 319
 320 config BUSYBOX_CONFIG_DMALLOC
 321         bool "Dmalloc"
 322
 323 config BUSYBOX_CONFIG_EFENCE
 324         bool "Electric-fence"
 325
 326 endchoice
 327
 328 config BUSYBOX_CONFIG_DEBUG_YANK_SUSv2
 329         bool "Disable obsolete features removed before SUSv3?"
 330         default y
 331         help
 332           This option will disable backwards compatability with SuSv2,
 333           specifically, old-style numeric options ('command -1 <file>')
 334           will not be supported in head, tail, and fold.  (Note: should
 335           yank from renice too.)
 336
 337 endmenu
 338
 339 menu 'Installation Options'
 340
 341 config BUSYBOX_CONFIG_INSTALL_NO_USR
 342         bool "Don't use /usr"
 343         default n
 344         help
 345           Disable use of /usr. Don't activate this option if you don't know
 346           that you really want this behaviour.
 347
 348 choice
 349        prompt "Applets links"
 350        default BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 351        help
 352          Choose how you install applets links.
 353
 354 config BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 355        bool "as soft-links"
 356        help
 357          Install applets as soft-links to the busybox binary. This needs some
 358          free inodes on the filesystem, but might help with filesystem
 359          generators that can't cope with hard-links.
 360
 361 config BUSYBOX_CONFIG_INSTALL_APPLET_HARDLINKS
 362        bool "as hard-links"
 363        help
 364          Install applets as hard-links to the busybox binary. This might count
 365          on a filesystem with few inodes.
 366
 367 config BUSYBOX_CONFIG_INSTALL_APPLET_DONT
 368        bool
 369        prompt "not installed"
 370        depends on BUSYBOX_CONFIG_FEATURE_INSTALLER || BUSYBOX_CONFIG_FEATURE_SH_STANDALONE_SHELL
 371        help
 372          Do not install applets links. Usefull when using the -install feature
 373          or a standalone shell for rescue pruposes.
 374
 375 endchoice
 376
 377 config BUSYBOX_PREFIX
 378         string
 379         default "./_install"
 380         help
 381           Define your directory to install BusyBox files/subdirs in.
 382
 383 endmenu
 384
 385 source package/busybox/config/libbb/Config.in
 386
 387 endmenu
 388
 389 comment "Applets"
 390
 391 source package/busybox/config/archival/Config.in
 392 source package/busybox/config/coreutils/Config.in
 393 source package/busybox/config/console-tools/Config.in
 394 source package/busybox/config/debianutils/Config.in
 395 source package/busybox/config/editors/Config.in
 396 source package/busybox/config/findutils/Config.in
 397 source package/busybox/config/init/Config.in
 398 source package/busybox/config/loginutils/Config.in
 399 source package/busybox/config/e2fsprogs/Config.in
 400 source package/busybox/config/modutils/Config.in
 401 source package/busybox/config/util-linux/Config.in
 402 source package/busybox/config/miscutils/Config.in
 403 source package/busybox/config/networking/Config.in
 404 source package/busybox/config/procps/Config.in
 405 source package/busybox/config/shell/Config.in
 406 source package/busybox/config/sysklogd/Config.in