Config.in 24 KB

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