openwrt/package/busybox/config/Config.in

   1 #
   2 # For a description of the syntax of this configuration file,
   3 # see scripts/kbuild/config-language.txt.
   4 #
   5
   6
   7 config BUSYBOX_HAVE_DOT_CONFIG
   8         bool
   9         default y
  10
  11 menu "General Configuration"
  12
  13 choice
  14         prompt "Buffer allocation policy"
  15         default BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  16         help
  17           There are 3 ways BusyBox can handle buffer allocations:
  18           - Use malloc. This costs code size for the call to xmalloc.
  19           - Put them on stack. For some very small machines with limited stack
  20             space, this can be deadly.  For most folks, this works just fine.
  21           - Put them in BSS. This works beautifully for computers with a real
  22             MMU (and OS support), but wastes runtime RAM for uCLinux. This
  23             behavior was the only one available for BusyBox versions 0.48 and
  24             earlier.
  25
  26 config BUSYBOX_CONFIG_FEATURE_BUFFERS_USE_MALLOC
  27         bool "Allocate with Malloc"
  28
  29 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  30         bool "Allocate on the Stack"
  31
  32 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_IN_BSS
  33         bool "Allocate in the .bss section"
  34
  35 endchoice
  36
  37 config BUSYBOX_CONFIG_FEATURE_VERBOSE_USAGE
  38         bool "Show verbose applet usage messages"
  39         default y
  40         help
  41           All BusyBox applets will show more verbose help messages when
  42           busybox is invoked with --help.  This will add a lot of text to the
  43           busybox binary.  In the default configuration, this will add about
  44           13k, but it can add much more depending on your configuration.
  45
  46 config BUSYBOX_CONFIG_FEATURE_INSTALLER
  47         bool "Support --install [-s] to install applet links at runtime"
  48         default n
  49         help
  50           Enable 'busybox --install [-s]' support.  This will allow you to use
  51           busybox at runtime to create hard links or symlinks for all the
  52           applets that are compiled into busybox.  This feature requires the
  53           /proc filesystem.
  54
  55 config BUSYBOX_CONFIG_LOCALE_SUPPORT
  56         bool "Enable locale support (system needs locale for this to work)"
  57         default n
  58         help
  59           Enable this if your system has locale support and you would like
  60           busybox to support locale settings.
  61
  62 config BUSYBOX_CONFIG_FEATURE_DEVFS
  63         bool "Support for devfs"
  64         default y
  65         help
  66           Enable if you want BusyBox to work with devfs.
  67
  68 config BUSYBOX_CONFIG_FEATURE_DEVPTS
  69         bool "Use the devpts filesystem for Unix98 PTYs"
  70         default y if BUSYBOX_CONFIG_FEATURE_DEVFS
  71         help
  72           Enable if you want BusyBox to use Unix98 PTY support. If enabled,
  73           busybox will use /dev/ptmx for the master side of the pseudoterminal
  74           and /dev/pts/<number> for the slave side.  Otherwise, BSD style
  75           /dev/ttyp<number> will be used. To use this option, you should have
  76           devpts or devfs mounted.
  77
  78 config BUSYBOX_CONFIG_FEATURE_CLEAN_UP
  79         bool "Clean up all memory before exiting (usually not needed)"
  80         default n
  81         help
  82           As a size optimization, busybox by default does not cleanup memory
  83           that is dynamically allocated or close files before exiting. This
  84           saves space and is usually not needed since the OS will clean up for
  85           us.  Don't enable this unless you have a really good reason to clean
  86           things up manually.
  87
  88 config BUSYBOX_CONFIG_FEATURE_SUID
  89         bool "Support for SUID/SGID handling"
  90         default y
  91         help
  92           Support SUID and SGID binaries.
  93
  94 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
  95         bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
  96         default n if BUSYBOX_CONFIG_FEATURE_SUID
  97         depends on BUSYBOX_CONFIG_FEATURE_SUID
  98         help
  99           Allow the SUID / SGID state of an applet to be determined runtime by
 100           checking /etc/busybox.conf.  The format of this file is as follows:
 101
 102           <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
 103
 104           An example might help:
 105
 106           [SUID]
 107           su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
 108           su = ssx        # exactly the same
 109
 110           mount = sx- root.disk # applet mount can be run by root and members of group disk
 111                                 # and runs with euid=0
 112
 113           cp = --- # disable applet cp for everyone
 114
 115           Robert 'sandman' Griebl has more information here:
 116           <url: http://www.softforge.de/bb/suid.html >.
 117
 118 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG_QUIET
 119         bool "Suppress warning message if /etc/busybox.conf is not readable"
 120         default n
 121         depends on BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 122         help
 123           /etc/busybox.conf should be readable by the user needing the SUID, check
 124           this option to avoid users to be notified about missing permissions.
 125
 126 config BUSYBOX_CONFIG_SELINUX
 127         bool "Support NSA Security Enhanced Linux"
 128         default n
 129         help
 130           Enable support for SE Linux in applets ls, ps, and id.  Also provide
 131           the option of compiling in SE Linux applets.
 132
 133           If you do not have a complete SE Linux Full Userland installed, this
 134           stuff will not compile.  Go visit
 135                 http://www.nsa.gov/selinux/index.html
 136           to download the necessary stuff to allow busybox to compile with this
 137           option enabled.
 138
 139           Most people will leave this set to 'N'.
 140
 141 endmenu
 142
 143 menu 'Build Options'
 144
 145 config BUSYBOX_CONFIG_STATIC
 146         bool "Build BusyBox as a static binary (no shared libs)"
 147         default n
 148         help
 149           If you want to build a static BusyBox binary, which does not
 150           use or require any shared libraries, then enable this option.
 151           This can cause BusyBox to be considerably larger, so you should
 152           leave this option false unless you have a good reason (i.e.
 153           your target platform does not support shared libraries, or
 154           you are building an initrd which doesn't need anything but
 155           BusyBox, etc).
 156
 157           Most people will leave this set to 'N'.
 158
 159 config BUSYBOX_CONFIG_LFS
 160         bool
 161         default y
 162         select BUSYBOX_FDISK_SUPPORT_LARGE_DISKS
 163         help
 164           If you want to build BusyBox with large file support, then enable
 165           this option.  This will have no effect if your kernel or your C
 166           library lacks large file support for large files.  Some of the
 167           programs that can benefit from large file support include dd, gzip,
 168           cp, mount, tar, and many others.  If you want to access files larger
 169           than 2 Gigabytes, enable this option.  Otherwise, leave it set to 'N'.
 170
 171 config BUSYBOX_USING_CROSS_COMPILER
 172         bool
 173         default y
 174         help
 175           Do you want to build BusyBox with a Cross Compiler?  If so,
 176           then enable this option.  Otherwise leave it set to 'N'.
 177
 178 config BUSYBOX_CROSS_COMPILER_PREFIX
 179         string
 180         default "mipsel-uclibc-"
 181         depends on BUSYBOX_USING_CROSS_COMPILER
 182         help
 183           If you want to build BusyBox with a cross compiler, then you
 184           will need to set this to the cross-compiler prefix.  For example,
 185           if my cross-compiler is /usr/i386-linux-uclibc/bin/i386-uclibc-gcc
 186           then I would enter '/usr/i386-linux-uclibc/bin/i386-uclibc-' here,
 187           which will ensure the correct compiler is used.
 188
 189 config BUSYBOX_EXTRA_CFLAGS_OPTIONS
 190         string
 191         default "-Os "
 192         help
 193           Do you want to pass any extra CFLAGS options to the compiler as
 194           you build BusyBox? If so, this is the option for you...  For example,
 195           if you want to add some simple compiler switches (like -march=i686),
 196           or check for warnings using -Werror, just those options here.
 197
 198 endmenu
 199
 200 menu 'Installation Options'
 201
 202 config BUSYBOX_CONFIG_INSTALL_NO_USR
 203         bool "Don't use /usr"
 204         default n
 205         help
 206           Disable use of /usr. Don't activate this option if you don't know
 207           that you really want this behaviour.
 208
 209 config BUSYBOX_PREFIX
 210         string
 211         default "./_install"
 212         help
 213           Define your directory to install BusyBox files/subdirs in.
 214
 215
 216
 217 endmenu
 218
 219 source package/busybox/config/archival/Config.in
 220 source package/busybox/config/coreutils/Config.in
 221 source package/busybox/config/console-tools/Config.in
 222 source package/busybox/config/debianutils/Config.in
 223 source package/busybox/config/editors/Config.in
 224 source package/busybox/config/findutils/Config.in
 225 source package/busybox/config/init/Config.in
 226 source package/busybox/config/loginutils/Config.in
 227 source package/busybox/config/miscutils/Config.in
 228 source package/busybox/config/modutils/Config.in
 229 source package/busybox/config/networking/Config.in
 230 source package/busybox/config/procps/Config.in
 231 source package/busybox/config/shell/Config.in
 232 source package/busybox/config/sysklogd/Config.in
 233 source package/busybox/config/util-linux/Config.in
 234
 235 menu 'Debugging Options'
 236
 237 config BUSYBOX_CONFIG_DEBUG
 238         bool "Build BusyBox with Debugging symbols"
 239         default n
 240         help
 241           Say Y here if you wish to compile BusyBox with debugging symbols.
 242           This will allow you to use a debugger to examine BusyBox internals
 243           while applets are running.  This increases the size of the binary
 244           considerably and should only be used when doing development.
 245           If you are doing development and want to debug BusyBox, answer Y.
 246
 247           Most people should answer N.
 248
 249 choice
 250         prompt "Additional debugging library"
 251         default BUSYBOX_CONFIG_NO_DEBUG_LIB
 252         depends on BUSYBOX_CONFIG_DEBUG
 253         help
 254           Using an additional debugging library will make BusyBox become
 255           considerable larger and will cause it to run more slowly.  You
 256           should always leave this option disabled for production use.
 257
 258           dmalloc support:
 259           ----------------
 260           This enables compiling with dmalloc ( http://dmalloc.com/ )
 261           which is an excellent public domain mem leak and malloc problem
 262           detector.  To enable dmalloc, before running busybox you will
 263           want to properly set your environment, for example:
 264             export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
 265           The 'debug=' value is generated using the following command
 266             dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
 267                -p check-fence -p check-heap -p check-lists -p check-blank \
 268                -p check-funcs -p realloc-copy -p allow-free-null
 269
 270           Electric-fence support:
 271           -----------------------
 272           This enables compiling with Electric-fence support.  Electric
 273           fence is another very useful malloc debugging library which uses
 274           your computer's virtual memory hardware to detect illegal memory
 275           accesses.  This support will make BusyBox be considerable larger
 276           and run slower, so you should leave this option disabled unless
 277           you are hunting a hard to find memory problem.
 278
 279
 280 config BUSYBOX_CONFIG_NO_DEBUG_LIB
 281         bool "None"
 282
 283 config BUSYBOX_CONFIG_DMALLOC
 284         bool "Dmalloc"
 285
 286 config BUSYBOX_CONFIG_EFENCE
 287         bool "Electric-fence"
 288
 289 endchoice
 290
 291
 292 endmenu
 293