[bug-mes] initial ELF scaffold for new architecture

[Jan Nieuwenhuizen]

Hi!

I just played with trying to add the `arm-mes-gcc' architecture, to get
a better feel for ARM.

Then I realised that the carefully crafted initial scaffolding up to the
first running executable that I created, has been removed with the most
recent Mes build simplification.

I intend to bring that back once I manage to simplify the build.  Just
for reference, this would be the initial binary

## x86 scaffold: Initial executable
## hex2 --LittleEndian --Architecture 1  --BaseAddress 0x1000000 -f 
lib/x86-mes/elf32-0header.hex2 -f lib/x86-mes/elf32-body-exit-42.hex2 -f 
lib/x86-mes/elf-0footer.hex2 --exec_enable -o lib/x86-mes/0exit-42.x86-out

## arm scaffold: Initial executable
hex2 --LittleEndian --Architecture 40  --BaseAddress 0x1000000 -f 
lib/arm-mes/elf32-0header.hex2 -f lib/arm-mes/elf32-body-exit-42.hex2 -f 
lib/arm-mes/elf-0footer.hex2 --exec_enable -o lib/arm-mes/0exit-42.arm-out

This scaffold and the next steps were removed in
http://git.savannah.gnu.org/cgit/mes.git/commit/?id=6b5ac576021f98358f1eb53315c667dfd9675fa7
,
the latest available version being 
http://git.savannah.gnu.org/cgit/mes.git/tree/build-aux/build-mes.sh?id=172879360e222f4b09cccaa45d3839e9e4d4e442

Greetings,
janneke

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com