English version
Accueil     À propos     Téléchargement     Ressources     Contactez-nous    

Ce site est rarement mis à jour. Pour les informations les plus récentes, rendez-vous sur le nouveau site OCaml à l'adresse ocaml.org.

Browse thread
[Caml-list] Linking confusion...
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2005-12-25 (23:45)
From: Jonathan Roewen <jonathan.roewen@g...>
Subject: [Caml-list] Linking confusion...

I'm looking at dynlinks makefile, which specifies a nice small list of
16 dependencies on .cmo files from compiler environment
(typing/utils/etc). Now my confusion comes on how it can link it
properly when symtable.cmo depends on other .cmos, which depend on yet
others (mainly through dependency on emitcode.cmo).

Now my question is: how can the dynlink library not only compile, but
also link if these dependencies aren't present? Does the bytecode
linker do dead code elimination to avoid dependencies on
modules/module functions not used?

And one smaller, off topic question: if these modules are in my kernel
environment (so I can use dynlink module), and say I dynlink
toplevellib.cma so I can use it at runtime, will it try to use the
already linked in modules in my kernel?