]> On Thu, Jul 17, 2003 at 10:37:55PM +0200, Xavier Leroy wrote: > There's a mismatch between the ocamlmklib approach and Windows DLLs > that has prevented me so far from making the former work with the > latter. > > Basically, ocamlmklib assumes that, from the *same* set of object C > files, one can build both > - a static library that can be statically linked with the Caml runtime system > and the application, and > - a shared library (DLL) that can be dynamically linked with the Caml > runtime system and the application. This is surely similar to the need for compiling C object files with -fPIC/-fpic under Linux if they are to become DLLs. Of course you /can/ compile without this flag, but as I understand it, if you do so you get shared libraries which aren't shared very effectively. Rich. -- Richard Jones. http://www.annexia.org/ http://freshmeat.net/users/rwmj Merjis Ltd. http://www.merjis.com/ - all your business data are belong to you. All new technology is irrelevant until it is taken up by the public. ------------------- 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