1
0

Config.in 27 KB

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