[Mono-dev] mkbundle assembler generation

[Hin-Tak Leung]

Hi,

(I am not subscribed to mono-devel so please cc:) . Recently I have played with mkbundle and monolinker and they are rather neat! So thanks.

I am wondering why mkbundle generates assembler, instead of say, C? according to the git log, it has been this way since day 1. What the generated assembler (but with 3 different headers for linux/windows/mac os platforms) basically amounts is something like this in C:

const unsigned char assembly_data_dllname[] = {hexdump};

I know doing it in assembler is faster (given that it is just a temporary file); but in terms of post-generation customization, it might be easier?
I suppose there are the possibility of padding and alignment issues if a C compiler is in the middle.

Hin-Tak Leung