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.
August 17th 2006: The server has moved to a new machine in Europe instead of the US.
Frequently Asked Questions (FAQ)
Wiki pages in continuous devel
Emdebian builds [:EmdebianToolchain:cross-toolchains] for use on standard Debian development machines. [http://www.emdebian.org/crosstools.html Repository details].
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.
[:Embedded_Debian_packaging_infrastructure:Embedded Debian Packaging Infrastructure] explains how the Emdebian repositories are organised, where the repositories are located and how to setup your system for emdebian uploads.
[:Embedded_Debian_packaging_rules:Emdebian packaging rules] details how emdebian packages should be built and organised.
- 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.
- 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.
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.
===2006=== May 14th - May 21st DebConf6EmdebianStuff
April 12-16 DebianEmbeddedWorkSessionExtremadura2006
February 25&26th [http://wiki.debian.org/EmDebian/Fosdem2006 Fosdem2006]