Difference between revisions of "Bering-uClibc 5.x - Developer Guide - Introduction"

From bering-uClibc
Jump to: navigation, search
m (moved Bering-uClibc-next - Developer Guide - Introduction to Bering-uClibc 5.x - Developer Guide - Introduction: The "next" version will be released as Bering-uClibc 5.x)
(Changed "next" references to 5.x)
 
Line 1: Line 1:
 
{| summary="Navigation header" width="100%"
 
{| summary="Navigation header" width="100%"
! colspan="3" align="center" | [[Bering-uClibc-next - Developer Guide - Introduction|Introduction]]
+
! colspan="3" align="center" | [[Bering-uClibc 5.x - Developer Guide - Introduction|Introduction]]
 
|-
 
|-
 
| width="20%" align="left"  |  
 
| width="20%" align="left"  |  
! width="60%" align="center" | [[Bering-uClibc-next - Developer Guide]]
+
! width="60%" align="center" | [[Bering-uClibc 5.x - Developer Guide]]
| width="20%" align="right"  | [[Bering-uClibc-next - Developer Guide - Preparing the Build Environment|Next]]
+
| width="20%" align="right"  | [[Bering-uClibc 5.x - Developer Guide - Preparing the Build Environment|Next]]
 
|}
 
|}
 
----
 
----
Line 10: Line 10:
  
 
This Developer Guide describes the recommended approach for people who want to:
 
This Developer Guide describes the recommended approach for people who want to:
* Build [[Bering-uClibc-next]] from source code.
+
* Build [[Bering-uClibc 5.x]] from source code.
 
* Modify an existing Package.
 
* Modify an existing Package.
 
* Add a new Package.
 
* Add a new Package.
Line 16: Line 16:
  
 
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.
 
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 [[Bering-uClibc-next - Developer Guide - Preparing the Build Environment|the next page]].
+
The build system needs to run Linux but it can be any modern distribution which includes the pre-requisites described on [[Bering-uClibc 5.x - Developer Guide - Preparing the Build Environment|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.
+
One major enhancement from [[Bering-uClibc 4.x]] is that the build environment can have a different architecture than target environment, because true cross-compilation is used.
  
  
For [[Bering-uClibc-next]] there is a well-developed toolchain which consists of:
+
For [[Bering-uClibc 5.x]] there is a well-developed toolchain which consists of:
 
* A utility called <code class="filename">buildtool.pl</code> which automates the process of compiling source code for Packages.
 
* A utility called <code class="filename">buildtool.pl</code> 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 <code class="filename">buildenv</code>.
+
** This also supports the compilation of the build environment itself, via a special pseudo-package called <code class="filename">toolchain</code>.
 
* A utility called <code class="filename">buildpacket.pl</code> which automates the process of assembling an installable Package (<tt>.lrp</tt>) file from compiled code.
 
* A utility called <code class="filename">buildpacket.pl</code> which automates the process of assembling an installable Package (<tt>.lrp</tt>) file from compiled code.
 
* A utility called <code class="filename">buildimage.pl</code> which automates the process of preparing a disk Image from a full set of Package files.
 
* A utility called <code class="filename">buildimage.pl</code> which automates the process of preparing a disk Image from a full set of Package files.
Line 31: Line 31:
 
{| summary="Navigation footer" width="100%"
 
{| summary="Navigation footer" width="100%"
 
| width="40%" align="left"  |  
 
| width="40%" align="left"  |  
| width="20%" align="center" | [[Bering-uClibc-next - Developer Guide|Up]]
+
| width="20%" align="center" | [[Bering-uClibc 5.x - Developer Guide|Up]]
| width="40%" align="right"  | [[Bering-uClibc-next - Developer Guide - Preparing the Build Environment|Next]]
+
| width="40%" align="right"  | [[Bering-uClibc 5.x - Developer Guide - Preparing the Build Environment|Next]]
 
|}
 
|}
  
[[Category:Bering-uClibc-next]]
+
[[Category:Bering-uClibc 5.x]]
 
[[Category:Developer Guide]]
 
[[Category:Developer Guide]]

Latest revision as of 21:19, 24 March 2012

Introduction
Bering-uClibc 5.x - Developer Guide Next


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

  • Build Bering-uClibc 5.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 "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 major enhancement from Bering-uClibc 4.x is that the build environment can have a different architecture than target environment, because true cross-compilation is used.


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