Bering-uClibc 4.x - Developer Guide - Introduction
From bering-uClibc
Revision as of 11:28, 19 December 2010 by Davidmbrooke (Talk | contribs) (General tidy-up and removed "future" note about buildimage.pl)
Introduction | ||
---|---|---|
Bering-uClibc 4.x - Developer Guide | Next |
This Developer Guide describes the recommended approach for people who want to:
- Build Bering-uClibc 4.x from source code.
- Modify an existing Package.
- Add a new Package.
All LEAF variants are designed to run on small, embedded systems which do not provide a suitable platform for software development. The distribution therefore needs to be prepared on a separate "host" system and installed onto the "target" system.
The host system needs to run Linux but it can be any modern distribution which includes the pre-requisites described on the next page.
One enhancement from Bering-uClibc 3.x is that the build environment can be 64-bit and still generate code for a 32-bit target system.
For Bering-uClibc 4.x there is a well-developed toolchain which consists of:
- A utility called
buildtool.pl
which automates the process of compiling source code for Packages.- This also supports the compilation of the build environment itself, via a special pseudo-package called
buildenv
.
- This also supports the compilation of the build environment itself, via a special pseudo-package called
- A utility called
buildpacket.pl
which automates the process of assembling an installable Package (.lrp) file from compiled code. - A utility called
buildimage.pl
which automates the process of preparing a disk Image from a full set of Package files.
Up | Next |