3
0

INSTALL 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142
  1. Building:
  2. =========
  3. The BusyBox build process is similar to the Linux kernel build:
  4. make menuconfig # This creates a file called ".config"
  5. make # This creates the "busybox" executable
  6. make install # or make CONFIG_PREFIX=/path/from/root install
  7. The full list of configuration and install options is available by typing:
  8. make help
  9. Quick Start:
  10. ============
  11. The easy way to try out BusyBox for the first time, without having to install
  12. it, is to enable all features and then use "standalone shell" mode with a
  13. blank command $PATH.
  14. To enable all features, use "make defconfig", which produces the largest
  15. general-purpose configuration. It's allyesconfig minus debugging options,
  16. optional packaging choices, and a few special-purpose features requiring
  17. extra configuration to use. Then enable "standalone shell" feature:
  18. make defconfig
  19. make menuconfig
  20. # select Busybox Settings
  21. # then General Configuration
  22. # then exec prefers applets
  23. # exit back to top level menu
  24. # select Shells
  25. # then Standalone shell
  26. # exit back to top level menu
  27. # exit and save new configuration
  28. # OR
  29. # use these commands to modify .config directly:
  30. sed -e 's/.*FEATURE_PREFER_APPLETS.*/CONFIG_FEATURE_PREFER_APPLETS=y/' -i .config
  31. sed -e 's/.*FEATURE_SH_STANDALONE.*/CONFIG_FEATURE_SH_STANDALONE=y/' -i .config
  32. make
  33. PATH= ./busybox ash
  34. Standalone shell mode causes busybox's built-in command shell to run
  35. any built-in busybox applets directly, without looking for external
  36. programs by that name. Supplying an empty command path (as above) means
  37. the only commands busybox can find are the built-in ones.
  38. Note that the standalone shell requires CONFIG_BUSYBOX_EXEC_PATH
  39. to be set appropriately, depending on whether or not /proc/self/exe is
  40. available. If you do not have /proc, then point that config option
  41. to the location of your busybox binary, usually /bin/busybox.
  42. Another solution is to patch the kernel (see
  43. examples/linux-*_proc_self_exe.patch) to make exec("/proc/self/exe")
  44. always work.
  45. Configuring Busybox:
  46. ====================
  47. Busybox is optimized for size, but enabling the full set of functionality
  48. still results in a fairly large executable -- more than 1 megabyte when
  49. statically linked. To save space, busybox can be configured with only the
  50. set of applets needed for each environment. The minimal configuration, with
  51. all applets disabled, produces a 4k executable. (It's useless, but very small.)
  52. The manual configurator "make menuconfig" modifies the existing configuration.
  53. (For systems without ncurses, try "make config" instead.) The two most
  54. interesting starting configurations are "make allnoconfig" (to start with
  55. everything disabled and add just what you need), and "make defconfig" (to
  56. start with everything enabled and remove what you don't need). If menuconfig
  57. is run without an existing configuration, make defconfig will run first to
  58. create a known starting point.
  59. Other starting configurations (mostly used for testing purposes) include
  60. "make allbareconfig" (enables all applets but disables all optional features),
  61. "make allyesconfig" (enables absolutely everything including debug features),
  62. and "make randconfig" (produce a random configuration). The configs/ directory
  63. contains a number of additional configuration files ending in _defconfig which
  64. are useful in specific cases. "make help" will list them.
  65. Configuring BusyBox produces a file ".config", which can be saved for future
  66. use. Run "make oldconfig" to bring a .config file from an older version of
  67. busybox up to date.
  68. Installing Busybox:
  69. ===================
  70. Busybox is a single executable that can behave like many different commands,
  71. and BusyBox uses the name it was invoked under to determine the desired
  72. behavior. (Try "mv busybox ls" and then "./ls -l".)
  73. Installing busybox consists of creating symlinks (or hardlinks) to the busybox
  74. binary for each applet enabled in busybox, and making sure these symlinks are
  75. in the shell's command $PATH. Running "make install" creates these symlinks,
  76. or "make install-hardlinks" creates hardlinks instead (useful on systems with
  77. a limited number of inodes). This install process uses the file
  78. "busybox.links" (created by make), which contains the list of enabled applets
  79. and the path at which to install them.
  80. Installing links to busybox is not always necessary. The special applet name
  81. "busybox" (or with any optional suffix, such as "busybox-static") uses the
  82. first argument to determine which applet to behave as, for example
  83. "./busybox cat LICENSE". (Running the busybox applet with no arguments gives
  84. a list of all enabled applets.) The standalone shell can also call busybox
  85. applets without links to busybox under other names in the filesystem. You can
  86. also configure a standalone install capability into the busybox base applet,
  87. and then install such links at runtime with one of "busybox --install" (for
  88. hardlinks) or "busybox --install -s" (for symlinks).
  89. If you enabled the busybox shared library feature (libbusybox.so) and want
  90. to run tests without installing, set your LD_LIBRARY_PATH accordingly when
  91. running the executable:
  92. LD_LIBRARY_PATH=`pwd` ./busybox
  93. Building out-of-tree:
  94. =====================
  95. By default, the BusyBox build puts its temporary files in the source tree.
  96. Building from a read-only source tree, or building multiple configurations from
  97. the same source directory, requires the ability to put the temporary files
  98. somewhere else.
  99. To build out of tree, cd to an empty directory and configure busybox from there:
  100. make KBUILD_SRC=/path/to/source -f /path/to/source/Makefile defconfig
  101. make
  102. make install
  103. Alternately, use the O=$BUILDPATH option (with an absolute path) during the
  104. configuration step, as in:
  105. make O=/some/empty/directory allyesconfig
  106. cd /some/empty/directory
  107. make
  108. make CONFIG_PREFIX=. install
  109. More Information:
  110. =================
  111. Se also the busybox FAQ, under the questions "How can I get started using
  112. BusyBox" and "How do I build a BusyBox-based system?" The BusyBox FAQ is
  113. available from http://www.busybox.net/FAQ.html