Browse thread
Native Module Linking
[
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: | -- (:) |
| From: | skaller <skaller@u...> |
| Subject: | Re: [Caml-list] Native Module Linking |
On Wed, 2004-11-10 at 05:38, Nicolas Cannasse wrote: > 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. > On windows everything works well but looks like on Linux some configurations > are not linking the plugins If you are not using code in a plugin, it won't be linked from a library .. and it also won't be a problem, because you're not using it .. that's the point of a library after all. Just place the cmx in the link command line to forcibly link it, to see the side effects of initialisation. -- John Skaller, mailto:skaller@users.sf.net voice: 061-2-9660-0850, snail: PO BOX 401 Glebe NSW 2037 Australia Checkout the Felix programming language http://felix.sf.net