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