make menuconfig # This creates a file called ".config"
make # This creates the "busybox" executable
- make install # or make PREFIX=/path/from/root install
+ make install # or make CONFIG_PREFIX=/path/from/root install
The full list of configuration and install options is available by typing:
programs by that name. Supplying an empty command path (as above) means
the only commands busybox can find are the built-in ones.
-(Note that the standalone shell currently requires /proc/self/exe to
-launch new applets.)
+Note that the standalone shell requires CONFIG_BUSYBOX_EXEC_PATH
+to be set appropriately, depending on whether or not /proc/self/exe is
+available or not. If you do not have /proc, then point that config option
+to the location of your busybox binary, usually /bin/busybox.
Configuring Busybox:
====================
create a known starting point.
Other starting configurations (mostly used for testing purposes) include
-"make allbaseconfig" (enables all applets but disables all optional features),
+"make allbareconfig" (enables all applets but disables all optional features),
"make allyesconfig" (enables absolutely everything including debug features),
and "make randconfig" (produce a random configuration).
make O=/some/empty/directory allyesconfig
cd /some/empty/directory
make
- make PREFIX=. install
+ make CONFIG_PREFIX=. install
More Information:
=================