Xavier Leroy <xavier.leroy@inria.fr> writes:

>> BTW, why Ocaml developers decided that ocamlopt should generate
>> camlprim?.c in C, but not directly in Assembler?
>
> Unless I'm mistaken, ocamlopt doesn't generate a camlprim.c file;
> ocamlc -custom does.  The reason for going through C in this case is
> that ocamlc has no knowledge of the assembly language for the
> processor: ocamlc is designed to work for any system that provides an
> ANSI C compiler.

Sorry, my mistake. But ocamlopt uses C compiler for linking. Why not to use
the link utility itself (say, link.exe for MSVC build)?

>> This is especially inconvenient for
>> Windows users where C compiler is not the part of OS distribution and
>> should be bought separately...
>
> We have addressed this issue in at least two different ways.  One is
> the dynamic loading of C/Caml stub code, as implemented since release
> 3.04.  Now is the time for external C libraries to use this mechanism,
> especially if they are to run under Windows.  The second answer to
> this problem is the Mingw port.  Don't complain about lack of options :-)

I am aware of MinGW port :-), but thank you for the detailed explanation.

- Dmitry Bely


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners