Select this only if you plan to use busybox on full-blown
desktop machine with common Linux distro, not on an embedded box.
-config FEATURE_ASSUME_UNICODE
- bool "Assume that 1:1 char/glyph correspondence is not true"
+config EXTRA_COMPAT
+ bool "Provide compatible behavior for rare corner cases (bigger code)"
default n
help
- This makes various applets aware that one byte is not
- one character on screen.
+ This option makes grep, sed etc handle rare corner cases
+ (embedded NUL bytes and such). This makes code bigger and uses
+ some GNU extensions in libc. You probably only need this option
+ if you plan to run busybox on desktop.
- Busybox aims to eventually work correctly with Unicode displays.
- Any older encodings are not guaranteed to work.
- Probably by the time when busybox will be fully Unicode-clean,
- other encodings will be mainly of historic interest.
+config INCLUDE_SUSv2
+ bool "Enable obsolete features removed before SUSv3"
+ default y
+ help
+ This option will enable backwards compatibility with SuSv2,
+ specifically, old-style numeric options ('command -1 <file>')
+ will be supported in head, tail, and fold. (Note: should
+ affect renice too.)
+
+config USE_PORTABLE_CODE
+ bool "Avoid using GCC-specific code constructs"
+ default n
+ help
+ Use this option if you are trying to compile busybox with
+ compiler other than gcc.
+ If you do use gcc, this option may needlessly increase code size.
choice
prompt "Buffer allocation policy"
Enable this if your system has locale support and you would like
busybox to support locale settings.
-config GETOPT_LONG
+config FEATURE_ASSUME_UNICODE
+ bool "Support Unicode"
+ default n
+ help
+ This makes various applets aware that one byte is not
+ one character on screen.
+
+ Busybox aims to eventually work correctly with Unicode displays.
+ Any older encodings are not guaranteed to work.
+ Probably by the time when busybox will be fully Unicode-clean,
+ other encodings will be mainly of historic interest.
+
+config FEATURE_CHECK_UNICODE_IN_ENV
+ bool "Check $LANG environment variable"
+ default y
+ depends on FEATURE_ASSUME_UNICODE && !LOCALE_SUPPORT
+ help
+ With this option on, Unicode support is activated
+ only if LANG variable has the value of the form "xxxx.utf8"
+
+ Otherwise, Unicode support will be always enabled and active.
+
+config SUBST_WCHAR
+ int "Character code to substitute unprintable characters with"
+ depends on FEATURE_ASSUME_UNICODE
+ default 63
+ help
+ Typical values are 63 for '?' (works with any output device),
+ 30 for ASCII substitute control code,
+ 65533 (0xfffd) for Unicode replacement character.
+
+config LAST_SUPPORTED_WCHAR
+ int "Range of supported Unicode characters"
+ depends on FEATURE_ASSUME_UNICODE
+ default 767
+ help
+ Any character with Unicode value bigger than this is assumed
+ to be non-printable on output device. Many applets replace
+ such chars with substitution character.
+
+ The idea is that many valid printable Unicode chars are
+ nevertheless are not displayed correctly. Think about
+ combining charachers, double-wide hieroglyphs, obscure
+ characters in dozens of ancient scripts...
+ Many terminals, terminal emulators, xterms etc will fail
+ to handle them correctly. Choose the smallest value
+ which suits your needs.
+
+ Typical values are:
+ 126 - ASCII only
+ 767 (0x2ff) - there are no combining chars in [0..767] range
+ (the range includes Latin 1, Latin Ext. A and B),
+ code is ~700 bytes smaller for this case.
+ 4351 (0x10ff) - there are no double-wide chars in [0..4351] range,
+ code is ~300 bytes smaller for this case.
+ 12799 (0x31ff) - nearly all non-ideographic characters are
+ available in [0..12799] range, including
+ East Asian scripts like katakana, hiragana, hangul,
+ bopomofo...
+ 0 - off, any valid printable Unicode character will be printed.
+
+config UNICODE_COMBINING_WCHARS
+ bool "Allow zero-width Unicode characters on output"
+ default n
+ depends on FEATURE_ASSUME_UNICODE
+ help
+ With this option off, any Unicode char with width of 0
+ is substituted on output.
+
+config UNICODE_WIDE_WCHARS
+ bool "Allow wide Unicode characters on output"
+ default n
+ depends on FEATURE_ASSUME_UNICODE
+ help
+ With this option off, any Unicode char with width > 1
+ is substituted on output.
+
+config UNICODE_BIDI_SUPPORT
+ bool "Bidirectional character-aware line input"
+ default y
+ depends on FEATURE_ASSUME_UNICODE && !LOCALE_SUPPORT
+ help
+ With this option on, right-to-left Unicode characters
+ are treated differently on input (e.g. cursor movement).
+
+config LONG_OPTS
bool "Support for --long-options"
default y
help
default n
help
With this option you can install the busybox binary belonging
- to root with the suid bit set, and it'll and it'll automatically drop
+ to root with the suid bit set, and it will automatically drop
priviledges for applets that don't need root access.
- If you're really paranoid and don't want to do this, build two
+ If you are really paranoid and don't want to do this, build two
busybox binaries with different applets in them (and the appropriate
symlinks pointing to each binary), and only set the suid bit on the
one that needs it. The applets currently marked to need the suid bit
- are login, passwd, su, ping, traceroute, crontab, dnsd, ipcrm, ipcs,
- and vlock.
+ are:
+
+ crontab, dnsd, findfs, ipcrm, ipcs, login, passwd, ping, su,
+ traceroute, vlock.
config FEATURE_SUID_CONFIG
bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
# These are auto-selected by other options
config FEATURE_SYSLOG
- bool "Support for logging to syslog"
+ bool #No description makes it a hidden option
default n
- help
- This option is auto-selected when you select any applet which may
- send its output to syslog. You do not need to select it manually.
+ #help
+ # This option is auto-selected when you select any applet which may
+ # send its output to syslog. You do not need to select it manually.
config FEATURE_HAVE_RPC
- bool "RPC support"
+ bool #No description makes it a hidden option
default n
- help
- This is automatically selected if any of enabled applets need it.
- You do not need to select it manually.
+ #help
+ # This is automatically selected if any of enabled applets need it.
+ # You do not need to select it manually.
endmenu
help
If you want to build BusyBox with a cross compiler, then you
will need to set this to the cross-compiler prefix, for example,
- "i386-uclibc-". Note that CROSS_COMPILE environment variable
- or "make CROSS_COMPILE=xxx ..." will override this selection.
- For native build leave it empty.
+ "i386-uclibc-".
+
+ Note that CROSS_COMPILE environment variable or
+ "make CROSS_COMPILE=xxx ..." will override this selection.
+
+ Native builds leave this empty.
+
+config EXTRA_CFLAGS
+ string "Additional CFLAGS"
+ default ""
+ help
+ Additional CFLAGS to pass to the compiler verbatim.
endmenu
endchoice
-config INCLUDE_SUSv2
- bool "Enable obsolete features removed before SUSv3?"
- default y
- help
- This option will enable backwards compatibility with SuSv2,
- specifically, old-style numeric options ('command -1 <file>')
- will be supported in head, tail, and fold. (Note: should
- affect renice too.)
-
-config PARSE
- bool "Uniform config file parser debugging applet: parse"
+### config PARSE
+### bool "Uniform config file parser debugging applet: parse"
endmenu
source util-linux/Config.in
source miscutils/Config.in
source networking/Config.in
+source printutils/Config.in
+source mailutils/Config.in
source procps/Config.in
-source shell/Config.in
-source sysklogd/Config.in
source runit/Config.in
source selinux/Config.in
-source printutils/Config.in
+source shell/Config.in
+source sysklogd/Config.in
projects / oweals / busybox.git / blobdiff