Hi, > Sure. It might be necessary to put some thoughts on how to > integrate the new native DLL feature best, though. > I'm currently on vacation and travelling, and cannot do > anything about it. Please have a bit of patience. I'm back > at end of December.
Hope you had a nice holiday. I think that for the most part, adding support for native dynlinking will happen naturally and gradually. I've been using it with the 3.10 release of GODI for over six months now (using a CVS HEAD version of the compiler, of course), and all works fine. The only required tweaks are as follows: 1) add this line to the META file for the dynlink package: archive(native) = "dynlink.cmxa" 2) For every package you want to natdynlink, create the .cmxs from the .cmxa file: ocamlopt -shared -linkall module.cmxa -o module.cmxs 3) Add the info about the bytecode/native plugin for findlib. I suggest using the Ocsigen convention of tagging the plugin with "plugin": (note that for byte code, the pluggable module is identical to the static version). archive(plugin,byte) = "module.cma" archive(plugin,native) = "module.cmxs" Now, I'm not sure if the GODI can automate steps 2 and 3. Even if not, it's not a problem if GODI 3.11 is released with few or no packages doing those steps; with time, packages will update their own build instructions. Cheers, Dario Teixeira _______________________________________________ Godi-list mailing list [email protected] https://godirepo.camlcity.org/mailman/listinfo/godi-list
