Mercurial > hg > aboriginal
changeset 382:0699ecc8b146
Update README to match current directory layout and system-image scripts.
author | Rob Landley <rob@landley.net> |
---|---|
date | Sat, 09 Aug 2008 12:08:00 -0500 |
parents | 40ddb3f4ed5d |
children | c0d571a25cd4 |
files | www/downloads/README |
diffstat | 1 files changed, 20 insertions(+), 10 deletions(-) [+] |
line wrap: on
line diff
--- a/www/downloads/README Thu Aug 07 20:20:56 2008 -0500 +++ b/www/downloads/README Sat Aug 09 12:08:00 2008 -0500 @@ -37,9 +37,9 @@ tarballs are there for historical reasons; the newest version is probably always the one you want. -cross-compiler: +binaries/cross-compiler: - The "cross-compiler" directory contains "host-i686" and "host-x86_64" + The "binaries/cross-compiler" directory contains "host-i686" and "host-x86_64" directories which contain prebuilt cross compilers which run on the appropriate type of host. The i686 versions were built under Ubuntu 6.06 and the x86_64 versions were built under Ubuntu 7.04. Each was built using the @@ -47,9 +47,9 @@ yourself these tarballs should be created in the "build" directory. Each cross-compiler-$ARCH tarball contains a compiler toolchain which - produces binaries or the given platform, linked against uClibc. (If you want - to build uClibc binaries on an x86 host, use the toolchain in - cross-compiler/host-i686/cross-compiler-i686.tar.bz2.) + produces binaries or the given platform, linked against uClibc. (If you + just want to build uClibc binaries on an x86 host, use the toolchain in + binaries/cross-compiler/host-i686/cross-compiler-i686.tar.bz2.) To use one of these compilers, extract the tarball and use the "$ARCH-gcc" binary as your compiler, which is located in the "bin" subdirectory. You @@ -61,7 +61,7 @@ Note: This cross compiler is small and simple and only supports C. The native compiler in mini-native supports C++ as well. -mini-native: +binaries/mini-native: Each mini-native-$ARCH tarball contains a minimal native root filesystem for the given platform. This filesystem is organized as a Linux From @@ -75,9 +75,9 @@ link the programs you build. For more information, see http://www.linuxfromscratch.org/lfs/view/stable/chapter06/chapter06.html -image: +binaries/system-image: - This directory contains three files per target architecture: + This directory contains tarballs with five files per target architecture: image-$ARCH.ext2.bz2: a bzipped ext2 filesystem image containing the files from the corresponding mini-native tarball. Run bunzip2 on this before @@ -85,7 +85,17 @@ zImage-$ARCH: a bootable Linux kernel configured for use with QEMU. - run-$ARCH.sh: a shell script that attempts to boot the corresponding ext2 + run-emulator.sh: shell script that attempts to boot the corresponding ext2 filesystem image and Linux kernel zImage files under the emulator QEMU - (version 0.9.0 or newer). The script expects to find both files in the + (version 0.9.1 or newer). The script expects to find both files in the current directory. + + run-with-home.sh: shell script that creates an empty 2 gigabyte ext2 image + named hdb.img, to act as a second hard drive for the emulator to mount on + /home. It then calls run-emulator.sh. (It will not recreate the image if it + already exists.) + + run-with-distcc.sh: a shell script that runs a distcc server hooked up to + the cross compiler for this architecture, and calls run-with-home.sh with + extra environment variables so the development environment inside the + emulator can call out to the cross compiler for extra speed.