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