source: branches/2.2.9/mindi-busybox/Config.in @ 2725

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