Differences between revisions 27 and 28
Revision 27 as of 2006-10-23 11:14:03
Size: 5147
Editor: HectorOron
Revision 28 as of 2006-11-02 15:46:49
Size: 5143
Editor: ?OllyBetts
Comment: fix typos
Deletions are marked like this. Additions are marked like this.
Line 65: Line 65:
 * bring Ed's framework upto date with Etch.  * bring Ed's framework up to date with Etch.
Line 68: Line 68:
 * promote DEB_BUILD_OPTIONS=notest for skipping tests   * promote DEB_BUILD_OPTIONS=notest for skipping tests
Line 70: Line 70:
 * Kill scratchbox in it's current form and make a better scratchbox2  * Kill scratchbox in its current form and make a better scratchbox2
Line 80: Line 80:
themselves.  themselves.
Line 83: Line 83:
toward smaller footprint to the packages.  toward smaller footprint to the packages.
Line 88: Line 88:
Optional :  Optional :

Adapted Debian tools so you can build/cross-compile DebianPackage s or adapted packages with info on how to cross-build and build smaller packages.

Emdebian is experimenting with different approaches to cross-building and small-system-friendly packages in order to produce sustainable and robust long-term solutions. For cross-building there are two main approaches: ["Scratchbox"], which allows cross-builds to appear to be native to the apps being built, and dpkg-cross which allows conventional cross-builds to occur in a Debian-compatible way. EmdebianSlind is a distribution built using dpkg-cross, and STAGE is built using scratchbox.

For package meta-data making packages more suitable for shrinking, two approaches are currently being investigated. The STAG approach uses a $(DEBIAN_DIR) directory to overlay changed info from the /debian directory, and is used by STAGE. The udeb approach of Debian-installer gives a tighter integration with Debian, with embedded packages having changed names so they can exist in the debian package namespace. Both mechanisms have pros and cons which are discussed in EmdebianMetaData.

Project Website


August 17th 2006: The server has moved to a new machine in Europe instead of the US. This is at until the DNS catches up. Expect some brokenness for the next couple of weeks until we have everything set up properly.

Frequently Asked Questions (FAQ)


Wiki pages in continuous devel


Cross Toolchains

Emdebian builds [EmdebianToolchain cross-toolchains] for use on standard Debian development machines. Currently tools for i386 & amd64 to arm, powerpc, mips, mipsel, m68k, alpha, ia64, s390, sparc and hppa are built for testing and unstable.

Add whichever of these lines your need to your /etc/apt/sources.list:

# EmDebian Toolchain [i386]
# deb http://www.emdebian.org/debian/ testing cross-testing
deb http://www.emdebian.org/debian/ unstable cross-unstable

If you are using AMD64,

# EmDebian Toolchain [AMD64]
# deb http://www.emdebian.org/debian/ testing cross-testing-amd64
deb http://www.emdebian.org/debian/ unstable cross-unstable-amd64

The "testing" and "unstable" distributions are currently synced with Debian mainstream.

To install the full toolchain (binutils, gcc, cpp, glibc), for e.g. ARM do:

 aptitude update
 aptitude install gcc-4.1-arm-linux

You will also need the development libraries (which will be brought in automatically if you auto-install Recommends:):

 aptitude install libc6-dev-arm-cross

You can alternatively install gcc-4.0-arm-linux, or for some arches where it builds. Other compilers are in the way.


EmdebianPackagingGuidelines is a document explaining to package maintainers the sorts of things they should be aware of in their packaging to make their packages 'Embedded-friendly'. This includes cross-building and small-system-building.


  • http://lists.debian.org/debian-embedded/2005/11/msg00014.html

    • Current state of affairs.
  • bring Ed's framework up to date with Etch.
  • create configurations for various devices and document howto do it
  • promote DEB_BUILD_OPTIONS=nodocs flag for not building docs
  • promote DEB_BUILD_OPTIONS=notest for skipping tests
  • co-operate with i386-uclibc team and embedded arch porters
  • Kill scratchbox in its current form and make a better scratchbox2
  • Settle and stick in to one of: familiar/ipkg, emdebian or udebs

Set-up a buildd inside scratchbox (which should be possible as I heard that it has already been done) to start building more packages. (This will hopefully be possible when the emdebian server is back up). (Once I find out how to silence my proliant server I might hook it up to my internet line and provide a secondary build env)

Document setting up the buildd so ["people"]/ ["dev"]s can try it out for themselves.

Integrate ["uclibc"] in the story. This will definitely give some size boost toward smaller footprint to the packages.

Once we have proven that this works start pushing things into Debian proper.

Optional :

  • Make sure everything works with the successors of scratchbox
  • Check the ARM build of Ubuntu

Well I hope I can open a fruitfull discussion with this and hope to see some more people starting to work on this.

See also: BootUsb , DebianRobot , EmDebian/DeBootstrap , EmDebian/CrossDebootstrap .

Wacky Ideas

There are also a few ideas that may need to be investigated further to decide whether it is a good idea to make them a new TODO item. These are collected on the EmdebianWackyIdeas page.

Work Sessions

February 25&26th [http://wiki.debian.org/EmDebian/Fosdem2006 Fosdem2006]

April 12-16 DebianEmbeddedWorkSessionExtremadura2006

May 14th - May 21st DebConf6EmdebianStuff