package/utils/busybox/config/Config.in

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