This is where cross-toolchains for various architectures are built.

buildcross is the script that does the work. You need to specify the
variables and some other parameters in
	/etc/buildcross.conf file
to finally run it and get a toolchain.

buildcross has been surrounded with many scripts and wrappers that
enhance toolchain builds. Now, it's a complete build infrastructure
where one only has to set the packages to build in the PKGLIST variable 
and ARCHLIST for the list of target architectures to build them for. 
Build logs are kept under the logs/ directory and there is an html file 
created recording the buildcross results. This can be displayed in a 
webserver to easily see the results.

buildcross is currently building Emdebian cross toolchains for nearly all
Debian arches, if bugs do not stop us.

Ah! buildcross gives no output, so it's best to run it in the background 
and check logs/ or from the html file: just do

Some notes on usage:

1) Configure /etc/buildcross.conf

2) run # buildcross -d
   -d shows some output
   -b quiet mode
   -h for help
 Output:
    check log.html and logs/
    build.log - buildcross log
    $host-$arch-$pkg.log - packages log

3) You can call some scripts manually
  ./em_clean.sh - removes arch dirs and removes toolchain packages

  I started to write most of the code for me to test. Since know i'll
start to document and giving it more coherence (as using /etc/buildcross.conf
in em_repro.sh,etc.) I'm also aiming to integrate emchain (||
em_cross.sh). I have also been thinking on patching or write some
system alike wanna-build but for emdebian, it would be good to keep in
mind to be posible to build in a distributed system (with many
computers). We should be preparing stuff to build a rootfs tarball for
all arches and provide a full set of cross toolchains, that's quitte a
work todo.

Emdebian team

