package/utils/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_CONFIG_HAVE_DOT_CONFIG
   8         bool
   9         default BUSYBOX_DEFAULT_HAVE_DOT_CONFIG
  10
  11 menu "Busybox Settings"
  12
  13 menu "General Configuration"
  14
  15 config BUSYBOX_CONFIG_DESKTOP
  16         bool "Enable options for full-blown desktop systems"
  17         default BUSYBOX_DEFAULT_DESKTOP
  18         help
  19           Enable options and features which are not essential.
  20           Select this only if you plan to use busybox on full-blown
  21           desktop machine with common Linux distro, not on an embedded box.
  22
  23 config BUSYBOX_CONFIG_EXTRA_COMPAT
  24         bool "Provide compatible behavior for rare corner cases (bigger code)"
  25         default BUSYBOX_DEFAULT_EXTRA_COMPAT
  26         help
  27           This option makes grep, sed etc handle rare corner cases
  28           (embedded NUL bytes and such). This makes code bigger and uses
  29           some GNU extensions in libc. You probably only need this option
  30           if you plan to run busybox on desktop.
  31
  32 config BUSYBOX_CONFIG_INCLUDE_SUSv2
  33         bool "Enable obsolete features removed before SUSv3"
  34         default BUSYBOX_DEFAULT_INCLUDE_SUSv2
  35         help
  36           This option will enable backwards compatibility with SuSv2,
  37           specifically, old-style numeric options ('command -1 <file>')
  38           will be supported in head, tail, and fold. (Note: should
  39           affect renice too.)
  40
  41 config BUSYBOX_CONFIG_USE_PORTABLE_CODE
  42         bool "Avoid using GCC-specific code constructs"
  43         default BUSYBOX_DEFAULT_USE_PORTABLE_CODE
  44         help
  45           Use this option if you are trying to compile busybox with
  46           compiler other than gcc.
  47           If you do use gcc, this option may needlessly increase code size.
  48
  49 config BUSYBOX_CONFIG_PLATFORM_LINUX
  50         bool "Enable Linux-specific applets and features"
  51         default BUSYBOX_DEFAULT_PLATFORM_LINUX
  52         help
  53           For the most part, busybox requires only POSIX compatibility
  54           from the target system, but some applets and features use
  55           Linux-specific interfaces.
  56
  57           Answering 'N' here will disable such applets and hide the
  58           corresponding configuration options.
  59
  60 choice
  61         prompt "Buffer allocation policy"
  62         default BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  63         help
  64           There are 3 ways BusyBox can handle buffer allocations:
  65           - Use malloc. This costs code size for the call to xmalloc.
  66           - Put them on stack. For some very small machines with limited stack
  67             space, this can be deadly. For most folks, this works just fine.
  68           - Put them in BSS. This works beautifully for computers with a real
  69             MMU (and OS support), but wastes runtime RAM for uCLinux. This
  70             behavior was the only one available for BusyBox versions 0.48 and
  71             earlier.
  72
  73 config BUSYBOX_CONFIG_FEATURE_BUFFERS_USE_MALLOC
  74         bool "Allocate with Malloc"
  75
  76 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  77         bool "Allocate on the Stack"
  78
  79 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_IN_BSS
  80         bool "Allocate in the .bss section"
  81
  82 endchoice
  83
  84 config BUSYBOX_CONFIG_SHOW_USAGE
  85         bool "Show applet usage messages"
  86         default BUSYBOX_DEFAULT_SHOW_USAGE
  87         help
  88           Enabling this option, BusyBox applets will show terse help messages
  89           when invoked with wrong arguments.
  90           If you do not want to show any (helpful) usage message when
  91           issuing wrong command syntax, you can say 'N' here,
  92           saving approximately 7k.
  93
  94 config BUSYBOX_CONFIG_FEATURE_VERBOSE_USAGE
  95         bool "Show verbose applet usage messages"
  96         default BUSYBOX_DEFAULT_FEATURE_VERBOSE_USAGE
  97         depends on BUSYBOX_CONFIG_SHOW_USAGE
  98         help
  99           All BusyBox applets will show verbose help messages when
 100           busybox is invoked with --help. This will add a lot of text to the
 101           busybox binary. In the default configuration, this will add about
 102           13k, but it can add much more depending on your configuration.
 103
 104 config BUSYBOX_CONFIG_FEATURE_COMPRESS_USAGE
 105         bool "Store applet usage messages in compressed form"
 106         default BUSYBOX_DEFAULT_FEATURE_COMPRESS_USAGE
 107         depends on BUSYBOX_CONFIG_SHOW_USAGE
 108         help
 109           Store usage messages in .bz compressed form, uncompress them
 110           on-the-fly when <applet> --help is called.
 111
 112           If you have a really tiny busybox with few applets enabled (and
 113           bunzip2 isn't one of them), the overhead of the decompressor might
 114           be noticeable. Also, if you run executables directly from ROM
 115           and have very little memory, this might not be a win. Otherwise,
 116           you probably want this.
 117
 118 config BUSYBOX_CONFIG_BUSYBOX
 119         bool "Include busybox applet"
 120         default BUSYBOX_DEFAULT_BUSYBOX
 121         help
 122           The busybox applet provides general help regarding busybox and
 123           allows the included applets to be listed.  It's also required
 124           if applet links are to be installed at runtime.
 125
 126           If you can live without these features disabling this will save
 127           some space.
 128
 129 config BUSYBOX_CONFIG_FEATURE_INSTALLER
 130         bool "Support --install [-s] to install applet links at runtime"
 131         default BUSYBOX_DEFAULT_FEATURE_INSTALLER
 132         depends on BUSYBOX_CONFIG_BUSYBOX
 133         help
 134           Enable 'busybox --install [-s]' support. This will allow you to use
 135           busybox at runtime to create hard links or symlinks for all the
 136           applets that are compiled into busybox.
 137
 138 config BUSYBOX_CONFIG_INSTALL_NO_USR
 139         bool "Don't use /usr"
 140         default BUSYBOX_DEFAULT_INSTALL_NO_USR
 141         help
 142           Disable use of /usr. busybox --install and "make install"
 143           will install applets only to /bin and /sbin,
 144           never to /usr/bin or /usr/sbin.
 145
 146 config BUSYBOX_CONFIG_LOCALE_SUPPORT
 147         bool "Enable locale support (system needs locale for this to work)"
 148         default BUSYBOX_DEFAULT_LOCALE_SUPPORT
 149         help
 150           Enable this if your system has locale support and you would like
 151           busybox to support locale settings.
 152
 153 config BUSYBOX_CONFIG_UNICODE_SUPPORT
 154         bool "Support Unicode"
 155         default BUSYBOX_DEFAULT_UNICODE_SUPPORT
 156         help
 157           This makes various applets aware that one byte is not
 158           one character on screen.
 159
 160           Busybox aims to eventually work correctly with Unicode displays.
 161           Any older encodings are not guaranteed to work.
 162           Probably by the time when busybox will be fully Unicode-clean,
 163           other encodings will be mainly of historic interest.
 164
 165 config BUSYBOX_CONFIG_UNICODE_USING_LOCALE
 166         bool "Use libc routines for Unicode (else uses internal ones)"
 167         default BUSYBOX_DEFAULT_UNICODE_USING_LOCALE
 168         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT && BUSYBOX_CONFIG_LOCALE_SUPPORT
 169         help
 170           With this option on, Unicode support is implemented using libc
 171           routines. Otherwise, internal implementation is used.
 172           Internal implementation is smaller.
 173
 174 config BUSYBOX_CONFIG_FEATURE_CHECK_UNICODE_IN_ENV
 175         bool "Check $LC_ALL, $LC_CTYPE and $LANG environment variables"
 176         default BUSYBOX_DEFAULT_FEATURE_CHECK_UNICODE_IN_ENV
 177         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT && !BUSYBOX_CONFIG_UNICODE_USING_LOCALE
 178         help
 179           With this option on, Unicode support is activated
 180           only if locale-related variables have the value of the form
 181           "xxxx.utf8"
 182
 183           Otherwise, Unicode support will be always enabled and active.
 184
 185 config BUSYBOX_CONFIG_SUBST_WCHAR
 186         int "Character code to substitute unprintable characters with"
 187         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 188         default BUSYBOX_DEFAULT_SUBST_WCHAR
 189         help
 190           Typical values are 63 for '?' (works with any output device),
 191           30 for ASCII substitute control code,
 192           65533 (0xfffd) for Unicode replacement character.
 193
 194 config BUSYBOX_CONFIG_LAST_SUPPORTED_WCHAR
 195         int "Range of supported Unicode characters"
 196         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 197         default BUSYBOX_DEFAULT_LAST_SUPPORTED_WCHAR
 198         help
 199           Any character with Unicode value bigger than this is assumed
 200           to be non-printable on output device. Many applets replace
 201           such chars with substitution character.
 202
 203           The idea is that many valid printable Unicode chars are
 204           nevertheless are not displayed correctly. Think about
 205           combining charachers, double-wide hieroglyphs, obscure
 206           characters in dozens of ancient scripts...
 207           Many terminals, terminal emulators, xterms etc will fail
 208           to handle them correctly. Choose the smallest value
 209           which suits your needs.
 210
 211           Typical values are:
 212           126 - ASCII only
 213           767 (0x2ff) - there are no combining chars in [0..767] range
 214                         (the range includes Latin 1, Latin Ext. A and B),
 215                         code is ~700 bytes smaller for this case.
 216           4351 (0x10ff) - there are no double-wide chars in [0..4351] range,
 217                         code is ~300 bytes smaller for this case.
 218           12799 (0x31ff) - nearly all non-ideographic characters are
 219                         available in [0..12799] range, including
 220                         East Asian scripts like katakana, hiragana, hangul,
 221                         bopomofo...
 222           0 - off, any valid printable Unicode character will be printed.
 223
 224 config BUSYBOX_CONFIG_UNICODE_COMBINING_WCHARS
 225         bool "Allow zero-width Unicode characters on output"
 226         default BUSYBOX_DEFAULT_UNICODE_COMBINING_WCHARS
 227         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 228         help
 229           With this option off, any Unicode char with width of 0
 230           is substituted on output.
 231
 232 config BUSYBOX_CONFIG_UNICODE_WIDE_WCHARS
 233         bool "Allow wide Unicode characters on output"
 234         default BUSYBOX_DEFAULT_UNICODE_WIDE_WCHARS
 235         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 236         help
 237           With this option off, any Unicode char with width > 1
 238           is substituted on output.
 239
 240 config BUSYBOX_CONFIG_UNICODE_BIDI_SUPPORT
 241         bool "Bidirectional character-aware line input"
 242         default BUSYBOX_DEFAULT_UNICODE_BIDI_SUPPORT
 243         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT && !BUSYBOX_CONFIG_UNICODE_USING_LOCALE
 244         help
 245           With this option on, right-to-left Unicode characters
 246           are treated differently on input (e.g. cursor movement).
 247
 248 config BUSYBOX_CONFIG_UNICODE_NEUTRAL_TABLE
 249         bool "In bidi input, support non-ASCII neutral chars too"
 250         default BUSYBOX_DEFAULT_UNICODE_NEUTRAL_TABLE
 251         depends on BUSYBOX_CONFIG_UNICODE_BIDI_SUPPORT
 252         help
 253           In most cases it's enough to treat only ASCII non-letters
 254           (i.e. punctuation, numbers and space) as characters
 255           with neutral directionality.
 256           With this option on, more extensive (and bigger) table
 257           of neutral chars will be used.
 258
 259 config BUSYBOX_CONFIG_UNICODE_PRESERVE_BROKEN
 260         bool "Make it possible to enter sequences of chars which are not Unicode"
 261         default BUSYBOX_DEFAULT_UNICODE_PRESERVE_BROKEN
 262         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 263         help
 264           With this option on, on line-editing input (such as used by shells)
 265           invalid UTF-8 bytes are not substituted with the selected
 266           substitution character.
 267           For example, this means that entering 'l', 's', ' ', 0xff, [Enter]
 268           at shell prompt will list file named 0xff (single char name
 269           with char value 255), not file named '?'.
 270
 271 config BUSYBOX_CONFIG_PAM
 272         bool "Support for PAM (Pluggable Authentication Modules)"
 273         default BUSYBOX_DEFAULT_PAM
 274         help
 275           Use PAM in some busybox applets (currently login and httpd) instead
 276           of direct access to password database.
 277
 278 config BUSYBOX_CONFIG_FEATURE_USE_SENDFILE
 279         bool "Use sendfile system call"
 280         default BUSYBOX_DEFAULT_FEATURE_USE_SENDFILE
 281         select BUSYBOX_CONFIG_PLATFORM_LINUX
 282         help
 283           When enabled, busybox will use the kernel sendfile() function
 284           instead of read/write loops to copy data between file descriptors
 285           (for example, cp command does this a lot).
 286           If sendfile() doesn't work, copying code falls back to read/write
 287           loop. sendfile() was originally implemented for faster I/O
 288           from files to sockets, but since Linux 2.6.33 it was extended
 289           to work for many more file types.
 290
 291 config BUSYBOX_CONFIG_LONG_OPTS
 292         bool "Support for --long-options"
 293         default BUSYBOX_DEFAULT_LONG_OPTS
 294         help
 295           Enable this if you want busybox applets to use the gnu --long-option
 296           style, in addition to single character -a -b -c style options.
 297
 298 config BUSYBOX_CONFIG_FEATURE_DEVPTS
 299         bool "Use the devpts filesystem for Unix98 PTYs"
 300         default BUSYBOX_DEFAULT_FEATURE_DEVPTS
 301         help
 302           Enable if you want BusyBox to use Unix98 PTY support. If enabled,
 303           busybox will use /dev/ptmx for the master side of the pseudoterminal
 304           and /dev/pts/<number> for the slave side. Otherwise, BSD style
 305           /dev/ttyp<number> will be used. To use this option, you should have
 306           devpts mounted.
 307
 308 config BUSYBOX_CONFIG_FEATURE_CLEAN_UP
 309         bool "Clean up all memory before exiting (usually not needed)"
 310         default BUSYBOX_DEFAULT_FEATURE_CLEAN_UP
 311         help
 312           As a size optimization, busybox normally exits without explicitly
 313           freeing dynamically allocated memory or closing files. This saves
 314           space since the OS will clean up for us, but it can confuse debuggers
 315           like valgrind, which report tons of memory and resource leaks.
 316
 317           Don't enable this unless you have a really good reason to clean
 318           things up manually.
 319
 320 config BUSYBOX_CONFIG_FEATURE_UTMP
 321         bool "Support utmp file"
 322         default BUSYBOX_DEFAULT_FEATURE_UTMP
 323         help
 324           The file /var/run/utmp is used to track who is currently logged in.
 325           With this option on, certain applets (getty, login, telnetd etc)
 326           will create and delete entries there.
 327           "who" applet requires this option.
 328
 329 config BUSYBOX_CONFIG_FEATURE_WTMP
 330         bool "Support wtmp file"
 331         default BUSYBOX_DEFAULT_FEATURE_WTMP
 332         depends on BUSYBOX_CONFIG_FEATURE_UTMP
 333         help
 334           The file /var/run/wtmp is used to track when users have logged into
 335           and logged out of the system.
 336           With this option on, certain applets (getty, login, telnetd etc)
 337           will append new entries there.
 338           "last" applet requires this option.
 339
 340 config BUSYBOX_CONFIG_FEATURE_PIDFILE
 341         bool "Support writing pidfiles"
 342         default BUSYBOX_DEFAULT_FEATURE_PIDFILE
 343         help
 344           This option makes some applets (e.g. crond, syslogd, inetd) write
 345           a pidfile at the configured PID_FILE_PATH.  It has no effect
 346           on applets which require pidfiles to run.
 347
 348 config BUSYBOX_CONFIG_PID_FILE_PATH
 349         string "Path to directory for pidfile"
 350         default BUSYBOX_DEFAULT_PID_FILE_PATH
 351         depends on BUSYBOX_CONFIG_FEATURE_PIDFILE
 352         help
 353           This is the default path where pidfiles are created.  Applets which
 354           allow you to set the pidfile path on the command line will override
 355           this value.  The option has no effect on applets that require you to
 356           specify a pidfile path.
 357
 358 config BUSYBOX_CONFIG_FEATURE_SUID
 359         bool "Support for SUID/SGID handling"
 360         default BUSYBOX_DEFAULT_FEATURE_SUID
 361         help
 362           With this option you can install the busybox binary belonging
 363           to root with the suid bit set, enabling some applets to perform
 364           root-level operations even when run by ordinary users
 365           (for example, mounting of user mounts in fstab needs this).
 366
 367           Busybox will automatically drop privileges for applets
 368           that don't need root access.
 369
 370           If you are really paranoid and don't want to do this, build two
 371           busybox binaries with different applets in them (and the appropriate
 372           symlinks pointing to each binary), and only set the suid bit on the
 373           one that needs it.
 374
 375           The applets which require root rights (need suid bit or
 376           to be run by root) and will refuse to execute otherwise:
 377           crontab, login, passwd, su, vlock, wall.
 378
 379           The applets which will use root rights if they have them
 380           (via suid bit, or because run by root), but would try to work
 381           without root right nevertheless:
 382           findfs, ping[6], traceroute[6], mount.
 383
 384           Note that if you DONT select this option, but DO make busybox
 385           suid root, ALL applets will run under root, which is a huge
 386           security hole (think "cp /some/file /etc/passwd").
 387
 388 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 389         bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
 390         default BUSYBOX_DEFAULT_FEATURE_SUID_CONFIG
 391         depends on BUSYBOX_CONFIG_FEATURE_SUID
 392         help
 393           Allow the SUID / SGID state of an applet to be determined at runtime
 394           by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
 395           The format of this file is as follows:
 396
 397           APPLET = [Ssx-][Ssx-][x-] [USER.GROUP]
 398
 399           s: USER or GROUP is allowed to execute APPLET.
 400              APPLET will run under USER or GROUP
 401              (reagardless of who's running it).
 402           S: USER or GROUP is NOT allowed to execute APPLET.
 403              APPLET will run under USER or GROUP.
 404              This option is not very sensical.
 405           x: USER/GROUP/others are allowed to execute APPLET.
 406              No UID/GID change will be done when it is run.
 407           -: USER/GROUP/others are not allowed to execute APPLET.
 408
 409           An example might help:
 410
 411           [SUID]
 412           su = ssx root.0 # applet su can be run by anyone and runs with
 413                           # euid=0/egid=0
 414           su = ssx        # exactly the same
 415
 416           mount = sx- root.disk # applet mount can be run by root and members
 417                                 # of group disk (but not anyone else)
 418                                 # and runs with euid=0 (egid is not changed)
 419
 420           cp = --- # disable applet cp for everyone
 421
 422           The file has to be owned by user root, group root and has to be
 423           writeable only by root:
 424                 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
 425           The busybox executable has to be owned by user root, group
 426           root and has to be setuid root for this to work:
 427                 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
 428
 429           Robert 'sandman' Griebl has more information here:
 430           <url: http://www.softforge.de/bb/suid.html >.
 431
 432 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG_QUIET
 433         bool "Suppress warning message if /etc/busybox.conf is not readable"
 434         default BUSYBOX_DEFAULT_FEATURE_SUID_CONFIG_QUIET
 435         depends on BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 436         help
 437           /etc/busybox.conf should be readable by the user needing the SUID,
 438           check this option to avoid users to be notified about missing
 439           permissions.
 440
 441 config BUSYBOX_CONFIG_SELINUX
 442         bool "Support NSA Security Enhanced Linux"
 443         default BUSYBOX_DEFAULT_SELINUX
 444         select BUSYBOX_CONFIG_PLATFORM_LINUX
 445         help
 446           Enable support for SELinux in applets ls, ps, and id. Also provide
 447           the option of compiling in SELinux applets.
 448
 449           If you do not have a complete SELinux userland installed, this stuff
 450           will not compile.  Specifially, libselinux 1.28 or better is
 451           directly required by busybox. If the installation is located in a
 452           non-standard directory, provide it by invoking make as follows:
 453                 CFLAGS=-I<libselinux-include-path> \
 454                 LDFLAGS=-L<libselinux-lib-path> \
 455                 make
 456
 457           Most people will leave this set to 'N'.
 458
 459 config BUSYBOX_CONFIG_FEATURE_PREFER_APPLETS
 460         bool "exec prefers applets"
 461         default BUSYBOX_DEFAULT_FEATURE_PREFER_APPLETS
 462         help
 463           This is an experimental option which directs applets about to
 464           call 'exec' to try and find an applicable busybox applet before
 465           searching the PATH. This is typically done by exec'ing
 466           /proc/self/exe.
 467           This may affect shell, find -exec, xargs and similar applets.
 468           They will use applets even if /bin/<applet> -> busybox link
 469           is missing (or is not a link to busybox). However, this causes
 470           problems in chroot jails without mounted /proc and with ps/top
 471           (command name can be shown as 'exe' for applets started this way).
 472
 473 config BUSYBOX_CONFIG_BUSYBOX_EXEC_PATH
 474         string "Path to BusyBox executable"
 475         default BUSYBOX_DEFAULT_BUSYBOX_EXEC_PATH
 476         help
 477           When Busybox applets need to run other busybox applets, BusyBox
 478           sometimes needs to exec() itself. When the /proc filesystem is
 479           mounted, /proc/self/exe always points to the currently running
 480           executable. If you haven't got /proc, set this to wherever you
 481           want to run BusyBox from.
 482
 483 # These are auto-selected by other options
 484
 485 config BUSYBOX_CONFIG_FEATURE_SYSLOG
 486         bool #No description makes it a hidden option
 487         default BUSYBOX_DEFAULT_FEATURE_SYSLOG
 488         #help
 489         #  This option is auto-selected when you select any applet which may
 490         #  send its output to syslog. You do not need to select it manually.
 491
 492 config BUSYBOX_CONFIG_FEATURE_HAVE_RPC
 493         bool #No description makes it a hidden option
 494         default BUSYBOX_DEFAULT_FEATURE_HAVE_RPC
 495         #help
 496         #  This is automatically selected if any of enabled applets need it.
 497         #  You do not need to select it manually.
 498
 499 endmenu
 500
 501 menu 'Build Options'
 502
 503 config BUSYBOX_CONFIG_STATIC
 504         bool "Build BusyBox as a static binary (no shared libs)"
 505         default BUSYBOX_DEFAULT_STATIC
 506         help
 507           If you want to build a static BusyBox binary, which does not
 508           use or require any shared libraries, then enable this option.
 509           This can cause BusyBox to be considerably larger, so you should
 510           leave this option false unless you have a good reason (i.e.
 511           your target platform does not support shared libraries, or
 512           you are building an initrd which doesn't need anything but
 513           BusyBox, etc).
 514
 515           Most people will leave this set to 'N'.
 516
 517 config BUSYBOX_CONFIG_PIE
 518         bool "Build BusyBox as a position independent executable"
 519         default BUSYBOX_DEFAULT_PIE
 520         depends on !BUSYBOX_CONFIG_STATIC
 521         help
 522           Hardened code option. PIE binaries are loaded at a different
 523           address at each invocation. This has some overhead,
 524           particularly on x86-32 which is short on registers.
 525
 526           Most people will leave this set to 'N'.
 527
 528 config BUSYBOX_CONFIG_NOMMU
 529         bool "Force NOMMU build"
 530         default BUSYBOX_DEFAULT_NOMMU
 531         help
 532           Busybox tries to detect whether architecture it is being
 533           built against supports MMU or not. If this detection fails,
 534           or if you want to build NOMMU version of busybox for testing,
 535           you may force NOMMU build here.
 536
 537           Most people will leave this set to 'N'.
 538
 539 # PIE can be made to work with BUILD_LIBBUSYBOX, but currently
 540 # build system does not support that
 541 config BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 542         bool "Build shared libbusybox"
 543         default BUSYBOX_DEFAULT_BUILD_LIBBUSYBOX
 544         depends on !BUSYBOX_CONFIG_FEATURE_PREFER_APPLETS && !BUSYBOX_CONFIG_PIE && !BUSYBOX_CONFIG_STATIC
 545         help
 546           Build a shared library libbusybox.so.N.N.N which contains all
 547           busybox code.
 548
 549           This feature allows every applet to be built as a tiny
 550           separate executable. Enabling it for "one big busybox binary"
 551           approach serves no purpose and increases code size.
 552           You should almost certainly say "no" to this.
 553
 554 ### config FEATURE_FULL_LIBBUSYBOX
 555 ###     bool "Feature-complete libbusybox"
 556 ###     default n if !FEATURE_SHARED_BUSYBOX
 557 ###     depends on BUILD_LIBBUSYBOX
 558 ###     help
 559 ###       Build a libbusybox with the complete feature-set, disregarding
 560 ###       the actually selected config.
 561 ###
 562 ###       Normally, libbusybox will only contain the features which are
 563 ###       used by busybox itself. If you plan to write a separate
 564 ###       standalone application which uses libbusybox say 'Y'.
 565 ###
 566 ###       Note: libbusybox is GPL, not LGPL, and exports no stable API that
 567 ###       might act as a copyright barrier. We can and will modify the
 568 ###       exported function set between releases (even minor version number
 569 ###       changes), and happily break out-of-tree features.
 570 ###
 571 ###       Say 'N' if in doubt.
 572
 573 config BUSYBOX_CONFIG_FEATURE_INDIVIDUAL
 574         bool "Produce a binary for each applet, linked against libbusybox"
 575         default BUSYBOX_DEFAULT_FEATURE_INDIVIDUAL
 576         depends on BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 577         help
 578           If your CPU architecture doesn't allow for sharing text/rodata
 579           sections of running binaries, but allows for runtime dynamic
 580           libraries, this option will allow you to reduce memory footprint
 581           when you have many different applets running at once.
 582
 583           If your CPU architecture allows for sharing text/rodata,
 584           having single binary is more optimal.
 585
 586           Each applet will be a tiny program, dynamically linked
 587           against libbusybox.so.N.N.N.
 588
 589           You need to have a working dynamic linker.
 590
 591 config BUSYBOX_CONFIG_FEATURE_SHARED_BUSYBOX
 592         bool "Produce additional busybox binary linked against libbusybox"
 593         default BUSYBOX_DEFAULT_FEATURE_SHARED_BUSYBOX
 594         depends on BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 595         help
 596           Build busybox, dynamically linked against libbusybox.so.N.N.N.
 597
 598           You need to have a working dynamic linker.
 599
 600 ### config BUILD_AT_ONCE
 601 ###     bool "Compile all sources at once"
 602 ###     default n
 603 ###     help
 604 ###       Normally each source-file is compiled with one invocation of
 605 ###       the compiler.
 606 ###       If you set this option, all sources are compiled at once.
 607 ###       This gives the compiler more opportunities to optimize which can
 608 ###       result in smaller and/or faster binaries.
 609 ###
 610 ###       Setting this option will consume alot of memory, e.g. if you
 611 ###       enable all applets with all features, gcc uses more than 300MB
 612 ###       RAM during compilation of busybox.
 613 ###
 614 ###       This option is most likely only beneficial for newer compilers
 615 ###       such as gcc-4.1 and above.
 616 ###
 617 ###       Say 'N' unless you know what you are doing.
 618
 619 config BUSYBOX_CONFIG_LFS
 620         bool
 621         default BUSYBOX_DEFAULT_LFS
 622         help
 623           If you want to build BusyBox with large file support, then enable
 624           this option. This will have no effect if your kernel or your C
 625           library lacks large file support for large files. Some of the
 626           programs that can benefit from large file support include dd, gzip,
 627           cp, mount, tar, and many others. If you want to access files larger
 628           than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
 629
 630 config BUSYBOX_CONFIG_CROSS_COMPILER_PREFIX
 631         string "Cross Compiler prefix"
 632         default BUSYBOX_DEFAULT_CROSS_COMPILER_PREFIX
 633         help
 634           If you want to build BusyBox with a cross compiler, then you
 635           will need to set this to the cross-compiler prefix, for example,
 636           "i386-uclibc-".
 637
 638           Note that CROSS_COMPILE environment variable or
 639           "make CROSS_COMPILE=xxx ..." will override this selection.
 640
 641           Native builds leave this empty.
 642
 643 config BUSYBOX_CONFIG_SYSROOT
 644         string "Path to sysroot"
 645         default BUSYBOX_DEFAULT_SYSROOT
 646         help
 647           If you want to build BusyBox with a cross compiler, then you
 648           might also need to specify where /usr/include and /usr/lib
 649           will be found.
 650
 651           For example, BusyBox can be built against an installed
 652           Android NDK, platform version 9, for ARM ABI with
 653
 654           CONFIG_SYSROOT=/opt/android-ndk/platforms/android-9/arch-arm
 655
 656           Native builds leave this empty.
 657
 658 config BUSYBOX_CONFIG_EXTRA_CFLAGS
 659         string "Additional CFLAGS"
 660         default BUSYBOX_DEFAULT_EXTRA_CFLAGS
 661         help
 662           Additional CFLAGS to pass to the compiler verbatim.
 663
 664 config BUSYBOX_CONFIG_EXTRA_LDFLAGS
 665         string "Additional LDFLAGS"
 666         default BUSYBOX_DEFAULT_EXTRA_LDFLAGS
 667         help
 668           Additional LDFLAGS to pass to the linker verbatim.
 669
 670 config BUSYBOX_CONFIG_EXTRA_LDLIBS
 671         string "Additional LDLIBS"
 672         default BUSYBOX_DEFAULT_EXTRA_LDLIBS
 673         help
 674           Additional LDLIBS to pass to the linker with -l.
 675
 676 endmenu
 677
 678 menu 'Debugging Options'
 679
 680 config BUSYBOX_CONFIG_DEBUG
 681         bool "Build BusyBox with extra Debugging symbols"
 682         default BUSYBOX_DEFAULT_DEBUG
 683         help
 684           Say Y here if you wish to examine BusyBox internals while applets are
 685           running. This increases the size of the binary considerably, and
 686           should only be used when doing development. If you are doing
 687           development and want to debug BusyBox, answer Y.
 688
 689           Most people should answer N.
 690
 691 config BUSYBOX_CONFIG_DEBUG_PESSIMIZE
 692         bool "Disable compiler optimizations"
 693         default BUSYBOX_DEFAULT_DEBUG_PESSIMIZE
 694         depends on BUSYBOX_CONFIG_DEBUG
 695         help
 696           The compiler's optimization of source code can eliminate and reorder
 697           code, resulting in an executable that's hard to understand when
 698           stepping through it with a debugger. This switches it off, resulting
 699           in a much bigger executable that more closely matches the source
 700           code.
 701
 702 config BUSYBOX_CONFIG_DEBUG_SANITIZE
 703         bool "Enable runtime sanitizers (ASAN/LSAN/USAN/etc...)"
 704         default BUSYBOX_DEFAULT_DEBUG_SANITIZE
 705         help
 706           Say Y here if you want to enable runtime sanitizers. These help
 707           catch bad memory accesses (e.g. buffer overflows), but will make
 708           the executable larger and slow down runtime a bit.
 709
 710           If you aren't developing/testing busybox, say N here.
 711
 712 config BUSYBOX_CONFIG_UNIT_TEST
 713         bool "Build unit tests"
 714         default BUSYBOX_DEFAULT_UNIT_TEST
 715         help
 716           Say Y here if you want to build unit tests (both the framework and
 717           test cases) as a Busybox applet. This results in bigger code, so you
 718           probably don't want this option in production builds.
 719
 720 config BUSYBOX_CONFIG_WERROR
 721         bool "Abort compilation on any warning"
 722         default BUSYBOX_DEFAULT_WERROR
 723         help
 724           Selecting this will add -Werror to gcc command line.
 725
 726           Most people should answer N.
 727
 728 choice
 729         prompt "Additional debugging library"
 730         default BUSYBOX_CONFIG_NO_DEBUG_LIB
 731         help
 732           Using an additional debugging library will make BusyBox become
 733           considerable larger and will cause it to run more slowly. You
 734           should always leave this option disabled for production use.
 735
 736           dmalloc support:
 737           ----------------
 738           This enables compiling with dmalloc ( http://dmalloc.com/ )
 739           which is an excellent public domain mem leak and malloc problem
 740           detector. To enable dmalloc, before running busybox you will
 741           want to properly set your environment, for example:
 742             export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
 743           The 'debug=' value is generated using the following command
 744             dmalloc -p log-stats -p log-non-free -p log-bad-space \
 745                -p log-elapsed-time -p check-fence -p check-heap \
 746                -p check-lists -p check-blank -p check-funcs -p realloc-copy \
 747                -p allow-free-null
 748
 749           Electric-fence support:
 750           -----------------------
 751           This enables compiling with Electric-fence support. Electric
 752           fence is another very useful malloc debugging library which uses
 753           your computer's virtual memory hardware to detect illegal memory
 754           accesses. This support will make BusyBox be considerable larger
 755           and run slower, so you should leave this option disabled unless
 756           you are hunting a hard to find memory problem.
 757
 758
 759 config BUSYBOX_CONFIG_NO_DEBUG_LIB
 760         bool "None"
 761
 762 config BUSYBOX_CONFIG_DMALLOC
 763         bool "Dmalloc"
 764
 765 config BUSYBOX_CONFIG_EFENCE
 766         bool "Electric-fence"
 767
 768 endchoice
 769
 770 endmenu
 771
 772 menu 'Installation Options ("make install" behavior)'
 773
 774 choice
 775         prompt "What kind of applet links to install"
 776         default BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 777         help
 778           Choose what kind of links to applets are created by "make install".
 779
 780 config BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 781         bool "as soft-links"
 782         help
 783           Install applets as soft-links to the busybox binary. This needs some
 784           free inodes on the filesystem, but might help with filesystem
 785           generators that can't cope with hard-links.
 786
 787 config BUSYBOX_CONFIG_INSTALL_APPLET_HARDLINKS
 788         bool "as hard-links"
 789         help
 790           Install applets as hard-links to the busybox binary. This might
 791           count on a filesystem with few inodes.
 792
 793 config BUSYBOX_CONFIG_INSTALL_APPLET_SCRIPT_WRAPPERS
 794         bool "as script wrappers"
 795         help
 796           Install applets as script wrappers that call the busybox binary.
 797
 798 config BUSYBOX_CONFIG_INSTALL_APPLET_DONT
 799         bool "not installed"
 800         help
 801           Do not install applet links. Useful when you plan to use
 802           busybox --install for installing links, or plan to use
 803           a standalone shell and thus don't need applet links.
 804
 805 endchoice
 806
 807 choice
 808         prompt "/bin/sh applet link"
 809         default BUSYBOX_CONFIG_INSTALL_SH_APPLET_SYMLINK
 810         depends on BUSYBOX_CONFIG_INSTALL_APPLET_SCRIPT_WRAPPERS
 811         help
 812           Choose how you install /bin/sh applet link.
 813
 814 config BUSYBOX_CONFIG_INSTALL_SH_APPLET_SYMLINK
 815         bool "as soft-link"
 816         help
 817           Install /bin/sh applet as soft-link to the busybox binary.
 818
 819 config BUSYBOX_CONFIG_INSTALL_SH_APPLET_HARDLINK
 820         bool "as hard-link"
 821         help
 822           Install /bin/sh applet as hard-link to the busybox binary.
 823
 824 config BUSYBOX_CONFIG_INSTALL_SH_APPLET_SCRIPT_WRAPPER
 825         bool "as script wrapper"
 826         help
 827           Install /bin/sh applet as script wrapper that calls
 828           the busybox binary.
 829
 830 endchoice
 831
 832 config BUSYBOX_CONFIG_PREFIX
 833         string "BusyBox installation prefix"
 834         default BUSYBOX_DEFAULT_PREFIX
 835         help
 836           Define your directory to install BusyBox files/subdirs in.
 837
 838 endmenu
 839
 840 source libbb/Config.in
 841
 842 endmenu
 843
 844 comment "Applets"
 845
 846 source archival/Config.in
 847 source coreutils/Config.in
 848 source console-tools/Config.in
 849 source debianutils/Config.in
 850 source editors/Config.in
 851 source findutils/Config.in
 852 source init/Config.in
 853 source loginutils/Config.in
 854 source e2fsprogs/Config.in
 855 source modutils/Config.in
 856 source util-linux/Config.in
 857 source miscutils/Config.in
 858 source networking/Config.in
 859 source printutils/Config.in
 860 source mailutils/Config.in
 861 source procps/Config.in
 862 source runit/Config.in
 863 source selinux/Config.in
 864 source shell/Config.in
 865 source sysklogd/Config.in