Bering-uClibc 5.x - Developer Guide - Introduction

From bering-uClibc
Revision as of 16:14, 6 December 2011 by Nitr0man (Talk | contribs) (Created page with '{| summary="Navigation header" width="100%" ! colspan="3" align="center" | Introduction |- | width="20%" align="left" | …')

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Introduction
Bering-uClibc-next - Developer Guide Next


This Developer Guide describes the recommended approach for people who want to:

  • Build Bering-uClibc-next 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 "build" system and installed onto the "target" system. The build 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 4.x is that the build environment can have different architecture that target arch, because true cross-compilation is used.


For Bering-uClibc-next 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.
  • 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