Config.in 29 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see scripts/kbuild/config-language.txt.
  4. #
  5. # mainmenu "BusyBox Configuration"
  6. config BUSYBOX_HAVE_DOT_CONFIG
  7. bool
  8. default y
  9. menu "Busybox Settings"
  10. menu "General Configuration"
  11. config BUSYBOX_DESKTOP
  12. bool "Enable options for full-blown desktop systems"
  13. default n
  14. help
  15. Enable options and features which are not essential.
  16. Select this only if you plan to use busybox on full-blown
  17. desktop machine with common Linux distro, not on an embedded box.
  18. config BUSYBOX_EXTRA_COMPAT
  19. bool "Provide compatible behavior for rare corner cases (bigger code)"
  20. default n
  21. help
  22. This option makes grep, sed etc handle rare corner cases
  23. (embedded NUL bytes and such). This makes code bigger and uses
  24. some GNU extensions in libc. You probably only need this option
  25. if you plan to run busybox on desktop.
  26. config BUSYBOX_INCLUDE_SUSv2
  27. bool "Enable obsolete features removed before SUSv3"
  28. default n
  29. help
  30. This option will enable backwards compatibility with SuSv2,
  31. specifically, old-style numeric options ('command -1 <file>')
  32. will be supported in head, tail, and fold. (Note: should
  33. affect renice too.)
  34. config BUSYBOX_USE_PORTABLE_CODE
  35. bool "Avoid using GCC-specific code constructs"
  36. default n
  37. help
  38. Use this option if you are trying to compile busybox with
  39. compiler other than gcc.
  40. If you do use gcc, this option may needlessly increase code size.
  41. config BUSYBOX_INSTALL_NO_USR
  42. bool "Don't use /usr"
  43. default n
  44. help
  45. Disable use of /usr. busybox --install and "make install"
  46. will install applets only to /bin and /sbin,
  47. never to /usr/bin or /usr/sbin.
  48. config BUSYBOX_PLATFORM_LINUX
  49. bool "Enable Linux-specific applets and features"
  50. default y
  51. help
  52. For the most part, busybox requires only POSIX compatibility
  53. from the target system, but some applets and features use
  54. Linux-specific interfaces.
  55. Answering 'N' here will disable such applets and hide the
  56. corresponding configuration options.
  57. choice
  58. prompt "Buffer allocation policy"
  59. default FEATURE_BUFFERS_USE_MALLOC
  60. help
  61. There are 3 ways BusyBox can handle buffer allocations:
  62. - Use malloc. This costs code size for the call to xmalloc.
  63. - Put them on stack. For some very small machines with limited stack
  64. space, this can be deadly. For most folks, this works just fine.
  65. - Put them in BSS. This works beautifully for computers with a real
  66. MMU (and OS support), but wastes runtime RAM for uCLinux. This
  67. behavior was the only one available for BusyBox versions 0.48 and
  68. earlier.
  69. config BUSYBOX_FEATURE_BUFFERS_USE_MALLOC
  70. bool "Allocate with Malloc"
  71. config BUSYBOX_FEATURE_BUFFERS_GO_ON_STACK
  72. bool "Allocate on the Stack"
  73. config BUSYBOX_FEATURE_BUFFERS_GO_IN_BSS
  74. bool "Allocate in the .bss section"
  75. endchoice
  76. config BUSYBOX_SHOW_USAGE
  77. bool "Show applet usage messages"
  78. default y
  79. help
  80. Enabling this option, BusyBox applets will show terse help messages
  81. when invoked with wrong arguments.
  82. If you do not want to show any (helpful) usage message when
  83. issuing wrong command syntax, you can say 'N' here,
  84. saving approximately 7k.
  85. config BUSYBOX_FEATURE_VERBOSE_USAGE
  86. bool "Show verbose applet usage messages"
  87. default y
  88. depends on BUSYBOX_SHOW_USAGE
  89. help
  90. All BusyBox applets will show verbose help messages when
  91. busybox is invoked with --help. This will add a lot of text to the
  92. busybox binary. In the default configuration, this will add about
  93. 13k, but it can add much more depending on your configuration.
  94. config BUSYBOX_FEATURE_COMPRESS_USAGE
  95. bool "Store applet usage messages in compressed form"
  96. default y
  97. depends on BUSYBOX_SHOW_USAGE
  98. help
  99. Store usage messages in .bz compressed form, uncompress them
  100. on-the-fly when <applet> --help is called.
  101. If you have a really tiny busybox with few applets enabled (and
  102. bunzip2 isn't one of them), the overhead of the decompressor might
  103. be noticeable. Also, if you run executables directly from ROM
  104. and have very little memory, this might not be a win. Otherwise,
  105. you probably want this.
  106. config BUSYBOX_BUSYBOX
  107. bool "Include busybox applet"
  108. default y
  109. help
  110. The busybox applet provides general help regarding busybox and
  111. allows the included applets to be listed. It's also required
  112. if applet links are to be installed at runtime.
  113. If you can live without these features disabling this will save
  114. some space.
  115. config BUSYBOX_FEATURE_INSTALLER
  116. bool "Support --install [-s] to install applet links at runtime"
  117. default n
  118. help
  119. Enable 'busybox --install [-s]' support. This will allow you to use
  120. busybox at runtime to create hard links or symlinks for all the
  121. applets that are compiled into busybox.
  122. config BUSYBOX_LOCALE_SUPPORT
  123. bool "Enable locale support (system needs locale for this to work)"
  124. default n
  125. help
  126. Enable this if your system has locale support and you would like
  127. busybox to support locale settings.
  128. config BUSYBOX_UNICODE_SUPPORT
  129. bool "Support Unicode"
  130. default y
  131. help
  132. This makes various applets aware that one byte is not
  133. one character on screen.
  134. Busybox aims to eventually work correctly with Unicode displays.
  135. Any older encodings are not guaranteed to work.
  136. Probably by the time when busybox will be fully Unicode-clean,
  137. other encodings will be mainly of historic interest.
  138. config BUSYBOX_UNICODE_USING_LOCALE
  139. bool "Use libc routines for Unicode (else uses internal ones)"
  140. default n
  141. depends on BUSYBOX_UNICODE_SUPPORT && BUSYBOX_LOCALE_SUPPORT
  142. help
  143. With this option on, Unicode support is implemented using libc
  144. routines. Otherwise, internal implementation is used.
  145. Internal implementation is smaller.
  146. config BUSYBOX_FEATURE_CHECK_UNICODE_IN_ENV
  147. bool "Check $LANG environment variable"
  148. default n
  149. depends on BUSYBOX_UNICODE_SUPPORT && !BUSYBOX_UNICODE_USING_LOCALE
  150. help
  151. With this option on, Unicode support is activated
  152. only if LANG variable has the value of the form "xxxx.utf8"
  153. Otherwise, Unicode support will be always enabled and active.
  154. config BUSYBOX_SUBST_WCHAR
  155. int "Character code to substitute unprintable characters with"
  156. depends on BUSYBOX_UNICODE_SUPPORT
  157. default 63
  158. help
  159. Typical values are 63 for '?' (works with any output device),
  160. 30 for ASCII substitute control code,
  161. 65533 (0xfffd) for Unicode replacement character.
  162. config BUSYBOX_LAST_SUPPORTED_WCHAR
  163. int "Range of supported Unicode characters"
  164. depends on BUSYBOX_UNICODE_SUPPORT
  165. default 767
  166. help
  167. Any character with Unicode value bigger than this is assumed
  168. to be non-printable on output device. Many applets replace
  169. such chars with substitution character.
  170. The idea is that many valid printable Unicode chars are
  171. nevertheless are not displayed correctly. Think about
  172. combining charachers, double-wide hieroglyphs, obscure
  173. characters in dozens of ancient scripts...
  174. Many terminals, terminal emulators, xterms etc will fail
  175. to handle them correctly. Choose the smallest value
  176. which suits your needs.
  177. Typical values are:
  178. 126 - ASCII only
  179. 767 (0x2ff) - there are no combining chars in [0..767] range
  180. (the range includes Latin 1, Latin Ext. A and B),
  181. code is ~700 bytes smaller for this case.
  182. 4351 (0x10ff) - there are no double-wide chars in [0..4351] range,
  183. code is ~300 bytes smaller for this case.
  184. 12799 (0x31ff) - nearly all non-ideographic characters are
  185. available in [0..12799] range, including
  186. East Asian scripts like katakana, hiragana, hangul,
  187. bopomofo...
  188. 0 - off, any valid printable Unicode character will be printed.
  189. config BUSYBOX_UNICODE_COMBINING_WCHARS
  190. bool "Allow zero-width Unicode characters on output"
  191. default n
  192. depends on BUSYBOX_UNICODE_SUPPORT
  193. help
  194. With this option off, any Unicode char with width of 0
  195. is substituted on output.
  196. config BUSYBOX_UNICODE_WIDE_WCHARS
  197. bool "Allow wide Unicode characters on output"
  198. default n
  199. depends on BUSYBOX_UNICODE_SUPPORT
  200. help
  201. With this option off, any Unicode char with width > 1
  202. is substituted on output.
  203. config BUSYBOX_UNICODE_BIDI_SUPPORT
  204. bool "Bidirectional character-aware line input"
  205. default n
  206. depends on BUSYBOX_UNICODE_SUPPORT && !BUSYBOX_UNICODE_USING_LOCALE
  207. help
  208. With this option on, right-to-left Unicode characters
  209. are treated differently on input (e.g. cursor movement).
  210. config BUSYBOX_UNICODE_NEUTRAL_TABLE
  211. bool "In bidi input, support non-ASCII neutral chars too"
  212. default n
  213. depends on BUSYBOX_UNICODE_BIDI_SUPPORT
  214. help
  215. In most cases it's enough to treat only ASCII non-letters
  216. (i.e. punctuation, numbers and space) as characters
  217. with neutral directionality.
  218. With this option on, more extensive (and bigger) table
  219. of neutral chars will be used.
  220. config BUSYBOX_UNICODE_PRESERVE_BROKEN
  221. bool "Make it possible to enter sequences of chars which are not Unicode"
  222. default n
  223. depends on BUSYBOX_UNICODE_SUPPORT
  224. help
  225. With this option on, on line-editing input (such as used by shells)
  226. invalid UTF-8 bytes are not substituted with the selected
  227. substitution character.
  228. For example, this means that entering 'l', 's', ' ', 0xff, [Enter]
  229. at shell prompt will list file named 0xff (single char name
  230. with char value 255), not file named '?'.
  231. config BUSYBOX_PAM
  232. bool "Support for PAM (Pluggable Authentication Modules)"
  233. default n
  234. help
  235. Use PAM in some busybox applets (currently login and httpd) instead
  236. of direct access to password database.
  237. config BUSYBOX_FEATURE_USE_SENDFILE
  238. bool "Use sendfile system call"
  239. default y
  240. select BUSYBOX_PLATFORM_LINUX
  241. help
  242. When enabled, busybox will use the kernel sendfile() function
  243. instead of read/write loops to copy data between file descriptors
  244. (for example, cp command does this a lot).
  245. If sendfile() doesn't work, copying code falls back to read/write
  246. loop. sendfile() was originally implemented for faster I/O
  247. from files to sockets, but since Linux 2.6.33 it was extended
  248. to work for many more file types.
  249. config BUSYBOX_LONG_OPTS
  250. bool "Support for --long-options"
  251. default y
  252. help
  253. Enable this if you want busybox applets to use the gnu --long-option
  254. style, in addition to single character -a -b -c style options.
  255. config BUSYBOX_FEATURE_DEVPTS
  256. bool "Use the devpts filesystem for Unix98 PTYs"
  257. default y
  258. help
  259. Enable if you want BusyBox to use Unix98 PTY support. If enabled,
  260. busybox will use /dev/ptmx for the master side of the pseudoterminal
  261. and /dev/pts/<number> for the slave side. Otherwise, BSD style
  262. /dev/ttyp<number> will be used. To use this option, you should have
  263. devpts mounted.
  264. config BUSYBOX_FEATURE_CLEAN_UP
  265. bool "Clean up all memory before exiting (usually not needed)"
  266. default n
  267. help
  268. As a size optimization, busybox normally exits without explicitly
  269. freeing dynamically allocated memory or closing files. This saves
  270. space since the OS will clean up for us, but it can confuse debuggers
  271. like valgrind, which report tons of memory and resource leaks.
  272. Don't enable this unless you have a really good reason to clean
  273. things up manually.
  274. config BUSYBOX_FEATURE_UTMP
  275. bool "Support utmp file"
  276. default n
  277. help
  278. The file /var/run/utmp is used to track who is currently logged in.
  279. With this option on, certain applets (getty, login, telnetd etc)
  280. will create and delete entries there.
  281. "who" applet requires this option.
  282. config BUSYBOX_FEATURE_WTMP
  283. bool "Support wtmp file"
  284. default n
  285. depends on BUSYBOX_FEATURE_UTMP
  286. help
  287. The file /var/run/wtmp is used to track when users have logged into
  288. and logged out of the system.
  289. With this option on, certain applets (getty, login, telnetd etc)
  290. will append new entries there.
  291. "last" applet requires this option.
  292. config BUSYBOX_FEATURE_PIDFILE
  293. bool "Support writing pidfiles"
  294. default y
  295. help
  296. This option makes some applets (e.g. crond, syslogd, inetd) write
  297. a pidfile in /var/run. Some applications rely on them.
  298. config BUSYBOX_PID_FILE_PATH
  299. string "Path to directory for pidfile"
  300. default "/var/run"
  301. depends on BUSYBOX_FEATURE_PIDFILE
  302. help
  303. This is the default path where pidfiles are created. Applets which
  304. allow you to set the pidfile path on the command line will override
  305. this value. The option has no effect on applets that require you to
  306. specify a pidfile path.
  307. config BUSYBOX_FEATURE_SUID
  308. bool "Support for SUID/SGID handling"
  309. default y
  310. help
  311. With this option you can install the busybox binary belonging
  312. to root with the suid bit set, enabling some applets to perform
  313. root-level operations even when run by ordinary users
  314. (for example, mounting of user mounts in fstab needs this).
  315. Busybox will automatically drop priviledges for applets
  316. that don't need root access.
  317. If you are really paranoid and don't want to do this, build two
  318. busybox binaries with different applets in them (and the appropriate
  319. symlinks pointing to each binary), and only set the suid bit on the
  320. one that needs it.
  321. The applets which require root rights (need suid bit or
  322. to be run by root) and will refuse to execute otherwise:
  323. crontab, login, passwd, su, vlock, wall.
  324. The applets which will use root rights if they have them
  325. (via suid bit, or because run by root), but would try to work
  326. without root right nevertheless:
  327. findfs, ping[6], traceroute[6], mount.
  328. Note that if you DONT select this option, but DO make busybox
  329. suid root, ALL applets will run under root, which is a huge
  330. security hole (think "cp /some/file /etc/passwd").
  331. config BUSYBOX_FEATURE_SUID_CONFIG
  332. bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
  333. default y
  334. depends on BUSYBOX_FEATURE_SUID
  335. help
  336. Allow the SUID / SGID state of an applet to be determined at runtime
  337. by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
  338. The format of this file is as follows:
  339. APPLET = [Ssx-][Ssx-][x-] [USER.GROUP]
  340. s: USER or GROUP is allowed to execute APPLET.
  341. APPLET will run under USER or GROUP
  342. (reagardless of who's running it).
  343. S: USER or GROUP is NOT allowed to execute APPLET.
  344. APPLET will run under USER or GROUP.
  345. This option is not very sensical.
  346. x: USER/GROUP/others are allowed to execute APPLET.
  347. No UID/GID change will be done when it is run.
  348. -: USER/GROUP/others are not allowed to execute APPLET.
  349. An example might help:
  350. [SUID]
  351. su = ssx root.0 # applet su can be run by anyone and runs with
  352. # euid=0/egid=0
  353. su = ssx # exactly the same
  354. mount = sx- root.disk # applet mount can be run by root and members
  355. # of group disk (but not anyone else)
  356. # and runs with euid=0 (egid is not changed)
  357. cp = --- # disable applet cp for everyone
  358. The file has to be owned by user root, group root and has to be
  359. writeable only by root:
  360. (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
  361. The busybox executable has to be owned by user root, group
  362. root and has to be setuid root for this to work:
  363. (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
  364. Robert 'sandman' Griebl has more information here:
  365. <url: http://www.softforge.de/bb/suid.html >.
  366. config BUSYBOX_FEATURE_SUID_CONFIG_QUIET
  367. bool "Suppress warning message if /etc/busybox.conf is not readable"
  368. default y
  369. depends on BUSYBOX_FEATURE_SUID_CONFIG
  370. help
  371. /etc/busybox.conf should be readable by the user needing the SUID,
  372. check this option to avoid users to be notified about missing
  373. permissions.
  374. config BUSYBOX_SELINUX
  375. bool "Support NSA Security Enhanced Linux"
  376. default n
  377. select BUSYBOX_PLATFORM_LINUX
  378. help
  379. Enable support for SELinux in applets ls, ps, and id. Also provide
  380. the option of compiling in SELinux applets.
  381. If you do not have a complete SELinux userland installed, this stuff
  382. will not compile. Go visit
  383. http://www.nsa.gov/selinux/index.html
  384. to download the necessary stuff to allow busybox to compile with
  385. this option enabled. Specifially, libselinux 1.28 or better is
  386. directly required by busybox. If the installation is located in a
  387. non-standard directory, provide it by invoking make as follows:
  388. CFLAGS=-I<libselinux-include-path> \
  389. LDFLAGS=-L<libselinux-lib-path> \
  390. make
  391. Most people will leave this set to 'N'.
  392. config BUSYBOX_FEATURE_PREFER_APPLETS
  393. bool "exec prefers applets"
  394. default n
  395. help
  396. This is an experimental option which directs applets about to
  397. call 'exec' to try and find an applicable busybox applet before
  398. searching the PATH. This is typically done by exec'ing
  399. /proc/self/exe.
  400. This may affect shell, find -exec, xargs and similar applets.
  401. They will use applets even if /bin/<applet> -> busybox link
  402. is missing (or is not a link to busybox). However, this causes
  403. problems in chroot jails without mounted /proc and with ps/top
  404. (command name can be shown as 'exe' for applets started this way).
  405. config BUSYBOX_BUSYBOX_EXEC_PATH
  406. string "Path to BusyBox executable"
  407. default "/proc/self/exe"
  408. help
  409. When Busybox applets need to run other busybox applets, BusyBox
  410. sometimes needs to exec() itself. When the /proc filesystem is
  411. mounted, /proc/self/exe always points to the currently running
  412. executable. If you haven't got /proc, set this to wherever you
  413. want to run BusyBox from.
  414. # These are auto-selected by other options
  415. config BUSYBOX_FEATURE_SYSLOG
  416. bool #No description makes it a hidden option
  417. default n
  418. #help
  419. # This option is auto-selected when you select any applet which may
  420. # send its output to syslog. You do not need to select it manually.
  421. config BUSYBOX_FEATURE_HAVE_RPC
  422. bool #No description makes it a hidden option
  423. default n
  424. #help
  425. # This is automatically selected if any of enabled applets need it.
  426. # You do not need to select it manually.
  427. endmenu
  428. menu 'Build Options'
  429. config BUSYBOX_STATIC
  430. bool "Build BusyBox as a static binary (no shared libs)"
  431. default y if ADK_STATIC
  432. default n
  433. help
  434. If you want to build a static BusyBox binary, which does not
  435. use or require any shared libraries, then enable this option.
  436. This can cause BusyBox to be considerably larger, so you should
  437. leave this option false unless you have a good reason (i.e.
  438. your target platform does not support shared libraries, or
  439. you are building an initrd which doesn't need anything but
  440. BusyBox, etc).
  441. Most people will leave this set to 'N'.
  442. config BUSYBOX_PIE
  443. bool "Build BusyBox as a position independent executable"
  444. default n
  445. depends on !BUSYBOX_STATIC
  446. help
  447. Hardened code option. PIE binaries are loaded at a different
  448. address at each invocation. This has some overhead,
  449. particularly on x86-32 which is short on registers.
  450. Most people will leave this set to 'N'.
  451. config BUSYBOX_NOMMU
  452. bool "Force NOMMU build"
  453. default n if ADK_TARGET_WITH_MMU
  454. default y
  455. help
  456. Busybox tries to detect whether architecture it is being
  457. built against supports MMU or not. If this detection fails,
  458. or if you want to build NOMMU version of busybox for testing,
  459. you may force NOMMU build here.
  460. Most people will leave this set to 'N'.
  461. # PIE can be made to work with BUILD_LIBBUSYBOX, but currently
  462. # build system does not support that
  463. config BUSYBOX_BUILD_LIBBUSYBOX
  464. bool "Build shared libbusybox"
  465. default n
  466. depends on !BUSYBOX_FEATURE_PREFER_APPLETS && !BUSYBOX_PIE && !BUSYBOX_STATIC
  467. help
  468. Build a shared library libbusybox.so.N.N.N which contains all
  469. busybox code.
  470. This feature allows every applet to be built as a tiny
  471. separate executable. Enabling it for "one big busybox binary"
  472. approach serves no purpose and increases code size.
  473. You should almost certainly say "no" to this.
  474. ### config FEATURE_FULL_LIBBUSYBOX
  475. ### bool "Feature-complete libbusybox"
  476. ### default n if !FEATURE_SHARED_BUSYBOX
  477. ### depends on BUSYBOX_BUILD_LIBBUSYBOX
  478. ### help
  479. ### Build a libbusybox with the complete feature-set, disregarding
  480. ### the actually selected config.
  481. ###
  482. ### Normally, libbusybox will only contain the features which are
  483. ### used by busybox itself. If you plan to write a separate
  484. ### standalone application which uses libbusybox say 'Y'.
  485. ###
  486. ### Note: libbusybox is GPL, not LGPL, and exports no stable API that
  487. ### might act as a copyright barrier. We can and will modify the
  488. ### exported function set between releases (even minor version number
  489. ### changes), and happily break out-of-tree features.
  490. ###
  491. ### Say 'N' if in doubt.
  492. config BUSYBOX_FEATURE_INDIVIDUAL
  493. bool "Produce a binary for each applet, linked against libbusybox"
  494. default y
  495. depends on BUSYBOX_BUILD_LIBBUSYBOX
  496. help
  497. If your CPU architecture doesn't allow for sharing text/rodata
  498. sections of running binaries, but allows for runtime dynamic
  499. libraries, this option will allow you to reduce memory footprint
  500. when you have many different applets running at once.
  501. If your CPU architecture allows for sharing text/rodata,
  502. having single binary is more optimal.
  503. Each applet will be a tiny program, dynamically linked
  504. against libbusybox.so.N.N.N.
  505. You need to have a working dynamic linker.
  506. config BUSYBOX_FEATURE_SHARED_BUSYBOX
  507. bool "Produce additional busybox binary linked against libbusybox"
  508. default y
  509. depends on BUSYBOX_BUILD_LIBBUSYBOX
  510. help
  511. Build busybox, dynamically linked against libbusybox.so.N.N.N.
  512. You need to have a working dynamic linker.
  513. ### config BUILD_AT_ONCE
  514. ### bool "Compile all sources at once"
  515. ### default n
  516. ### help
  517. ### Normally each source-file is compiled with one invocation of
  518. ### the compiler.
  519. ### If you set this option, all sources are compiled at once.
  520. ### This gives the compiler more opportunities to optimize which can
  521. ### result in smaller and/or faster binaries.
  522. ###
  523. ### Setting this option will consume alot of memory, e.g. if you
  524. ### enable all applets with all features, gcc uses more than 300MB
  525. ### RAM during compilation of busybox.
  526. ###
  527. ### This option is most likely only beneficial for newer compilers
  528. ### such as gcc-4.1 and above.
  529. ###
  530. ### Say 'N' unless you know what you are doing.
  531. config BUSYBOX_LFS
  532. bool "Build with Large File Support (for accessing files > 2 GB)"
  533. default y
  534. help
  535. If you want to build BusyBox with large file support, then enable
  536. this option. This will have no effect if your kernel or your C
  537. library lacks large file support for large files. Some of the
  538. programs that can benefit from large file support include dd, gzip,
  539. cp, mount, tar, and many others. If you want to access files larger
  540. than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
  541. config BUSYBOX_CROSS_COMPILER_PREFIX
  542. string "Cross Compiler prefix"
  543. default ""
  544. help
  545. If you want to build BusyBox with a cross compiler, then you
  546. will need to set this to the cross-compiler prefix, for example,
  547. "i386-uclibc-".
  548. Note that CROSS_COMPILE environment variable or
  549. "make CROSS_COMPILE=xxx ..." will override this selection.
  550. Native builds leave this empty.
  551. config BUSYBOX_SYSROOT
  552. string "Path to sysroot"
  553. default ""
  554. help
  555. If you want to build BusyBox with a cross compiler, then you
  556. might also need to specify where /usr/include and /usr/lib
  557. will be found.
  558. For example, BusyBox can be built against an installed
  559. Android NDK, platform version 9, for ARM ABI with
  560. CONFIG_SYSROOT=/opt/android-ndk/platforms/android-9/arch-arm
  561. Native builds leave this empty.
  562. config BUSYBOX_EXTRA_CFLAGS
  563. string "Additional CFLAGS"
  564. default ""
  565. help
  566. Additional CFLAGS to pass to the compiler verbatim.
  567. config BUSYBOX_EXTRA_LDFLAGS
  568. string "Additional LDFLAGS"
  569. default ""
  570. help
  571. Additional LDFLAGS to pass to the linker verbatim.
  572. config BUSYBOX_EXTRA_LDLIBS
  573. string "Additional LDLIBS"
  574. default ""
  575. help
  576. Additional LDLIBS to pass to the linker with -l.
  577. endmenu
  578. menu 'Debugging Options'
  579. config BUSYBOX_DEBUG
  580. bool "Build BusyBox with extra Debugging symbols"
  581. default n
  582. help
  583. Say Y here if you wish to examine BusyBox internals while applets are
  584. running. This increases the size of the binary considerably, and
  585. should only be used when doing development. If you are doing
  586. development and want to debug BusyBox, answer Y.
  587. Most people should answer N.
  588. config BUSYBOX_DEBUG_PESSIMIZE
  589. bool "Disable compiler optimizations"
  590. default n
  591. depends on BUSYBOX_DEBUG
  592. help
  593. The compiler's optimization of source code can eliminate and reorder
  594. code, resulting in an executable that's hard to understand when
  595. stepping through it with a debugger. This switches it off, resulting
  596. in a much bigger executable that more closely matches the source
  597. code.
  598. config BUSYBOX_DEBUG_SANITIZE
  599. bool "Enable runtime sanitizers (ASAN/LSAN/USAN/etc...)"
  600. default n
  601. help
  602. Say Y here if you want to enable runtime sanitizers. These help
  603. catch bad memory accesses (e.g. buffer overflows), but will make
  604. the executable larger and slow down runtime a bit.
  605. If you aren't developing/testing busybox, say N here.
  606. config BUSYBOX_UNIT_TEST
  607. bool "Build unit tests"
  608. default n
  609. help
  610. Say Y here if you want to build unit tests (both the framework and
  611. test cases) as a Busybox applet. This results in bigger code, so you
  612. probably don't want this option in production builds.
  613. config BUSYBOX_WERROR
  614. bool "Abort compilation on any warning"
  615. default n
  616. help
  617. Selecting this will add -Werror to gcc command line.
  618. Most people should answer N.
  619. choice
  620. prompt "Additional debugging library"
  621. default NO_DEBUG_LIB
  622. help
  623. Using an additional debugging library will make BusyBox become
  624. considerable larger and will cause it to run more slowly. You
  625. should always leave this option disabled for production use.
  626. dmalloc support:
  627. ----------------
  628. This enables compiling with dmalloc ( http://dmalloc.com/ )
  629. which is an excellent public domain mem leak and malloc problem
  630. detector. To enable dmalloc, before running busybox you will
  631. want to properly set your environment, for example:
  632. export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
  633. The 'debug=' value is generated using the following command
  634. dmalloc -p log-stats -p log-non-free -p log-bad-space \
  635. -p log-elapsed-time -p check-fence -p check-heap \
  636. -p check-lists -p check-blank -p check-funcs -p realloc-copy \
  637. -p allow-free-null
  638. Electric-fence support:
  639. -----------------------
  640. This enables compiling with Electric-fence support. Electric
  641. fence is another very useful malloc debugging library which uses
  642. your computer's virtual memory hardware to detect illegal memory
  643. accesses. This support will make BusyBox be considerable larger
  644. and run slower, so you should leave this option disabled unless
  645. you are hunting a hard to find memory problem.
  646. config BUSYBOX_NO_DEBUG_LIB
  647. bool "None"
  648. config BUSYBOX_DMALLOC
  649. bool "Dmalloc"
  650. config BUSYBOX_EFENCE
  651. bool "Electric-fence"
  652. endchoice
  653. endmenu
  654. menu 'Installation Options ("make install" behavior)'
  655. choice
  656. prompt "What kind of applet links to install"
  657. default INSTALL_APPLET_SYMLINKS
  658. help
  659. Choose what kind of links to applets are created by "make install".
  660. config BUSYBOX_INSTALL_APPLET_SYMLINKS
  661. bool "as soft-links"
  662. help
  663. Install applets as soft-links to the busybox binary. This needs some
  664. free inodes on the filesystem, but might help with filesystem
  665. generators that can't cope with hard-links.
  666. config BUSYBOX_INSTALL_APPLET_HARDLINKS
  667. bool "as hard-links"
  668. help
  669. Install applets as hard-links to the busybox binary. This might
  670. count on a filesystem with few inodes.
  671. config BUSYBOX_INSTALL_APPLET_SCRIPT_WRAPPERS
  672. bool "as script wrappers"
  673. help
  674. Install applets as script wrappers that call the busybox binary.
  675. config BUSYBOX_INSTALL_APPLET_DONT
  676. bool "not installed"
  677. help
  678. Do not install applet links. Useful when you plan to use
  679. busybox --install for installing links, or plan to use
  680. a standalone shell and thus don't need applet links.
  681. endchoice
  682. choice
  683. prompt "/bin/sh applet link"
  684. default INSTALL_SH_APPLET_SYMLINK
  685. depends on BUSYBOX_INSTALL_APPLET_SCRIPT_WRAPPERS
  686. help
  687. Choose how you install /bin/sh applet link.
  688. config BUSYBOX_INSTALL_SH_APPLET_SYMLINK
  689. bool "as soft-link"
  690. help
  691. Install /bin/sh applet as soft-link to the busybox binary.
  692. config BUSYBOX_INSTALL_SH_APPLET_HARDLINK
  693. bool "as hard-link"
  694. help
  695. Install /bin/sh applet as hard-link to the busybox binary.
  696. config BUSYBOX_INSTALL_SH_APPLET_SCRIPT_WRAPPER
  697. bool "as script wrapper"
  698. help
  699. Install /bin/sh applet as script wrapper that calls
  700. the busybox binary.
  701. endchoice
  702. config BUSYBOX_PREFIX
  703. string "BusyBox installation prefix"
  704. default "@IDIR@"
  705. help
  706. Define your directory to install BusyBox files/subdirs in.
  707. endmenu
  708. source package/busybox/config/libbb/Config.in
  709. endmenu
  710. comment "Applets"
  711. source package/busybox/config/archival/Config.in
  712. source package/busybox/config/coreutils/Config.in
  713. source package/busybox/config/console-tools/Config.in
  714. source package/busybox/config/debianutils/Config.in
  715. source package/busybox/config/editors/Config.in
  716. source package/busybox/config/findutils/Config.in
  717. source package/busybox/config/init/Config.in
  718. source package/busybox/config/loginutils/Config.in
  719. source package/busybox/config/e2fsprogs/Config.in
  720. source package/busybox/config/modutils/Config.in
  721. source package/busybox/config/util-linux/Config.in
  722. source package/busybox/config/miscutils/Config.in
  723. source package/busybox/config/networking/Config.in
  724. source package/busybox/config/printutils/Config.in
  725. source package/busybox/config/mailutils/Config.in
  726. source package/busybox/config/procps/Config.in
  727. source package/busybox/config/runit/Config.in
  728. source package/busybox/config/selinux/Config.in
  729. source package/busybox/config/shell/Config.in
  730. source package/busybox/config/sysklogd/Config.in