Sat Sep 18 20:07:19 CEST 2010

Compilation to .a for eCos

I don't like the eCosPro build system.  Let's make it so that it
compiles with simple eCos tools, and produces a library that can be
linked as a whole into the project.

After setting the -I (and -L) paths, the show stopper is the current
module system, as it is not separated into posix/non-posix.

Should I create leaf_posix and ex_posix modules?

Done that.  This makes config a bit harder though: when to include
ex_posix in sc.c for example?