On 25/03/15 12:14, Justin Cormack wrote:
Yes, frankenlibc works like that too. I will probably move the -F
flags parsing to subr.sh as at the moment I have it duplicated, as if
you do ./buildc -F ACLFLAGS=-m32 I need to extract that and use it to
compile the parts that are not compiled with rumpmake
I made buildrump.sh generate rumptools/toolchain-conf.mk for that purpose.
Are you planning to merge frankenlibc into rumprun soon? While I'm
"de-dupping" xen and baremetal, I could do frankenlibc too.
Also, summarizing the proposed terminology:
architecture = CPU ISA
platform = the layer above architecture (baremetal, frankenlibc, xen)
board = specific hardware configuration (probably valid only for
/baremetal?)
Frankenlibc is not a platform, it has platforms (inconsistently called
OS in the Makefiles but platform in the code), these are currently
linux, freebsd, netbsd, and are autodetected from the compiler, but
that wont be the case eg with most of the microkernels which use
generic compilers so you will need to specify.
Hmm, the OS sounds like -b(oard). Except that it's not a board per se,
just sounds and looks like one.
Existing baremetal platform should probably be called "pc" or similar.
I think I prefer a two-level hierarchy (especially since I'm assuming
that rumprun will be huge in 5 years ;)
