1
0

Config.in 28 KB

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