emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

s/PREFIX/CONFIG_PREFIX/

Browse Source
This commit is contained in:
Denis Vlasenko 2007-02-03 17:29:14 +00:00
parent 06af216528
commit e8ce0626d9
7 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
INSTALL
View File

@ -5,7 +5,7 @@ The BusyBox build process is similar to the Linux kernel build:
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:
@ -114,7 +114,7 @@ configuration step, as in:
make O=/some/empty/directory allyesconfig
cd /some/empty/directory
make
make PREFIX=. install
make CONFIG_PREFIX=. install
More Information:
=================

2
Makefile.help
View File

@ -27,7 +27,7 @@ help:
@echo ' make SED="$(objtree)/sed"'
@echo
@echo 'Installation:'
@echo ' install - install busybox into $(PREFIX)'
@echo ' install - install busybox into $(CONFIG_PREFIX)'
@echo ' uninstall'
@echo
@echo 'Development:'

8
README
View File

@ -50,10 +50,10 @@ Using busybox:
The build automatically generates a file "busybox.links", which is used by
'make install' to create symlinks to the BusyBox binary for all compiled in
commands. This uses the PREFIX environment variable to specify where to
install, and installs hardlinks or symlinks depending on the configuration
preferences. (You can also manually run the install script at
"applets/install.sh").
commands. This uses the CONFIG_PREFIX environment variable to specify
where to install, and installs hardlinks or symlinks depending
on the configuration preferences. (You can also manually run
the install script at "applets/install.sh").
----------------

10
docs/busybox_header.pod
View File

@ -33,11 +33,11 @@ menuconfig' to select the functionality that you wish to enable. Then run
After the compile has finished, you should use 'make install' to install
BusyBox. This will install the 'bin/busybox' binary, in the target directory
specified by PREFIX. PREFIX can be set when configuring BusyBox, or you can
specify an alternative location at install time (i.e., with a command line
like 'make PREFIX=/tmp/foo install'). If you enabled any applet installation
scheme (either as symlinks or hardlinks), these will also be installed in
the location pointed to by PREFIX.
specified by CONFIG_PREFIX. CONFIG_PREFIX can be set when configuring BusyBox,
or you can specify an alternative location at install time (i.e., with a
command line like 'make CONFIG_PREFIX=/tmp/foo install'). If you enabled
any applet installation scheme (either as symlinks or hardlinks), these will
also be installed in the location pointed to by CONFIG_PREFIX.
=head1 USAGE

2
examples/bootfloppy/bootfloppy.txt
View File

@ -72,7 +72,7 @@ The following steps will create a root file system.
- Install the Busybox binary and accompanying symlinks:
(chdir to busybox directory)
make PREFIX=(path to)loop/ install
make CONFIG_PREFIX=(path to)loop/ install
- Make device files in /dev:

2
examples/bootfloppy/mkrootfs.sh
View File

@ -76,7 +76,7 @@ cd $BASE_DIR
cd $BUSYBOX_DIR
make distclean
make CC=$BASE_DIR/$UCLIBC_DIR/extra/gcc-uClibc/i386-uclibc-gcc
make PREFIX=$BASE_DIR/$TARGET_DIR install
make CONFIG_PREFIX=$BASE_DIR/$TARGET_DIR install
cd $BASE_DIR

2
examples/busybox.spec
View File

@ -34,7 +34,7 @@ make
%Install
rm -rf $RPM_BUILD_ROOT
make PREFIX=$RPM_BUILD_ROOT install
make CONFIG_PREFIX=$RPM_BUILD_ROOT install
%Clean
rm -rf $RPM_BUILD_ROOT