Differences between revisions 2 and 3
Revision 2 as of 2006-05-16 05:01:56
Size: 1639
Editor: wookey
Comment: Categorise
Revision 3 as of 2006-05-17 17:27:06
Size: 1643
Editor: HectorOron
Comment: fixed title "background"
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
==Background== === Background ===

Debian has historically been packaged with desktop systems and native building in mind. It is increasingly being used in low-resource and embedded systems. Building natively on such systems is extremely slow and sometimes almost impossible, so cross-compiling is very important, and the normal way of building.

There is a number of things in packaging which affect how embedded-friendly they are. Here we explain some of the things you should do to make sure that your packages are suitable for embedded use. If you have questions please use the [ debian-embedded mailing list | http://lists.debian.org/debian-embedded/ ]


Below are various examples of things you should do/avoid doing, but it is best if you understand why these things are done. Here is some explanation of the issues.

Terminology (build/host/target).

  • build/target machines
  • build-time/install-time/run-time deps
  • build-arch deps/ target-arch deps
  • minimal base system - 4Mb not 200 Mb
  • busybox-friendly scripts
  • splitting out docs, optional tools, examples, languages
  • Install scripts - install-time (on build machine), riun-time (on target machine)

Things to mention:

  • reducing build-dependecies
    • - just removing unneeded stuff (sometimes pkgs have Build-Deps
      • which are not really needed)
      - move docu and other arch indep stuff to arch:all packages