[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2004-11-09 (21:53) |
From: | Nicolas Cannasse <warplayer@f...> |
Subject: | Re: [Caml-list] Native Module Linking |
> > Hi, > > > > I have a project that is structured like this : > > - a library with one Entry module and several Plugins > > - an application using the library. > > > > In the application I'm doing the following : > > > > open Entry; > > open Plugin1; > > open Plugin2; > > .... > > (* use "Entry" *) > > > > Plugins are using Entry, and application is only activating plugins with > > "open" (in order to ensure they're linked). > > open has no effect on linking, all it does is allow > you to use unqualified names. It depends exactly on what information basis linking is done For example, ocamldep works at syntax level and will report a dependency if an open is done. Ocamlopt could (should ?) enforce such dependency when an "open" directive is found, since ocamlc and ocamlopt-win32 are working correctly with it. Nicolas Cannasse