diff options
| author | Eric Andersen <andersen@codepoet.org> | 2001-08-10 08:00:08 +0000 |
|---|---|---|
| committer | Eric Andersen <andersen@codepoet.org> | 2001-08-10 08:00:08 +0000 |
| commit | 96277cfcea64ba6965b20fd78529f2f6fa59e32a (patch) | |
| tree | 69692cef15440ff2a45bf0429482f7f23a25b902 /README | |
| parent | 7e79b9d3abb86bc457607ff3405052092cbf0069 (diff) | |
Update the build system, yet again. I hope this is the last time...
Here is the basic theory of operation:
SHARED_LIB_LOADER_PATH/ <The location where the shared lib
loader will be installed and where the
compiler will cause apps to look for it.>
DEVEL_PREFIX/
bin/ <contains gcc, ld, etc for setting PATH=$DEVEL_PREFIX/bin:$PATH>
lib/ <contains all runtime and static libs>
include/ <Where all the header files go>
SYSTEM_DEVEL_PREFIX/
usr/bin/ <contains arch-uclibc-gcc, arch-uclibc-ld, etc that
might be installed by a .deb or .rpm into /usr/bin,
but can happily live under DEVEL_PREFIX>
PREFIX
This is prepended during 'make install's allowing you to shift things to
be installed under some alternate location (such as when building a .deb)
-Erik
Diffstat (limited to 'README')
| -rw-r--r-- | README | 22 |
1 files changed, 8 insertions, 14 deletions
@@ -3,12 +3,11 @@ cp ./extra/Configs/Config.<target arch> ./Config -Then edit ./Config for your setup. In particular, modify -CROSS and KERNEL_SOURCE as necessary. You may also want -to modify PREFIX if you want to install the development -environment to /usr/local/ or elsewhere. By default, the -development environment is installed into /usr and -/usr/<arch>-linux-uclibc/. +Then edit ./Config for your setup. In particular, modify CROSS and +KERNEL_SOURCE as necessary. You may also want to modify +SHARED_LIB_LOADER_PATH, DEVEL_PREFIX, and SYSTEM_DEVEL_PREFIX depending +on where you want to install the development environment. By default, +the development environment is installed into /usr/<arch>-linux-uclibc/. * Building: @@ -25,21 +24,16 @@ development environment is installed into /usr and This will install the header files, libraries, and the gcc wrapper into the directories defined in Config. -If you are targetting the same architecture as the host machine, -you may want to add a link from /lib/ld-uClibc.0 to the location -where ld-uClibc.0 was installed. This allows you to run binaries -compiled against uClibc without contaminating /lib too much. - * Installing the target runtime environment: (As root, if necessary,) - make TARGET_PREFIX=`pwd`/_install install_target + make PREFIX=<temporary path> install_target This installs only the files that are necessary to run binaries -compiled against uClibc. Hint: You really don't want to install -the target runtime environment on the host machine. +compiled against uClibc. Hint: You probably do not want to install +the target runtime environment on your host machine. * Using uClibc: |