From 9acf46c0c74008440f6dfc4d09d82934a56ecd18 Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Wed, 12 Jan 2005 07:52:50 +0000 Subject: Update docs for release --- docs/uclibc.org/toolchains.html | 120 ++++++++++++++++++++++++++-------------- 1 file changed, 80 insertions(+), 40 deletions(-) (limited to 'docs/uclibc.org/toolchains.html') diff --git a/docs/uclibc.org/toolchains.html b/docs/uclibc.org/toolchains.html index 132270b6b..852096af9 100644 --- a/docs/uclibc.org/toolchains.html +++ b/docs/uclibc.org/toolchains.html @@ -2,51 +2,91 @@

Toolchains

-To use uClibc, you need to have a toolchain, which is composed -of binutils, -gcc, and of course uClibc. +To use uClibc, you need to have a toolchain. A toolchain consists +of GNU binutils, +the gcc compiler, and uClibc, all +built to produce binaries for your target system linked with uClibc. +You can build your own native uClibc toolchain using the +uClibc buildroot system. +

+To build your own uClibc toolchain, follow the following simple +steps:

+ + + + +

+ +If you want to be really lazy and start using uClibc right away +without needing to compile your own toolchain or anything, you can grab a +pre-compiled uClibc development system. These are currently available for + +arm, +armeb, +i386, +mips, +mipsel, +powerpc, and +sh4. -

  • You can build your own - uClibc toolchain - using this to automagically download all the needed source code - and compile everything for you. -

    - -

  • Steven J. Hill has kindly provided - RPMs and SRPMs - with toolchains for mips. -

    - -

  • You can compile your own uClibc development system using - buildroot. -

    - -

  • Prebuilt uClibc development systems for - i386 - and - arm - and - mipsel - are available and contain complete native gcc 3.3.2 toolchains. These - are development systems are ext2 filesystems that runs natively on the - specified architecture. They contain all the development software you - need to build your own uClibc applications, including bash, coreutils, - findutils, diffutils, patch, sed, ed, flex, bison, file, gawk, tar, - grep gdb, strace, make, gcc, g++, autoconf, automake, ncurses, zlib, - openssl, openssh perl, and more. And of course, everything is - dynamically linked against uClibc. By using a uClibc only system, you - can avoid all the painful cross-configuration problems that have made - using uClibc somewhat painful in the past. If you want to quickly get - started with testing or using uClibc you should give these images a - try. You can loop mount them and then chroot into them. You can boot - into them using user-mode Linux. You can even 'dd' them to a spare - partition and use resize2fs to make them fill the drive, and then boot - into them. Whatever works for you. -

    +

    +These are bzip2 compressed ext2 filesystems containing all the development +software you need to build your own uClibc applications, including: bash, awk, +make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh, gdb, +strace, busybox, GNU coreutils, GNU tar, GNU grep, etc. + +

    + +Each of these uClibc development systems was created using +buildroot, specifically, +buildroot.tar.bz2 +along with these sources. + +

    + +These development systems should provide pretty much everything you need to get +started building your own applications with uClibc. Once you download one of +these systems, you can then boot into it, loop mount it, dd it to a spare drive +and use a tool such as resize2fs to make it fill a partition... Whatever works +best for you. + +

    +The quickest way to get started using a root_fs image (using the i386 +platform as an example) is: +

    +Type "exit" to end the chroot session and return to your host system. +

    + -- cgit v1.2.3