From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id A0831BB81 for ; Tue, 9 Nov 2004 22:53:48 +0100 (CET) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id iA9LrmIN011516 for ; Tue, 9 Nov 2004 22:53:48 +0100 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id WAA29413 for ; Tue, 9 Nov 2004 22:53:47 +0100 (MET) Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id iA9LrlL0015352 for ; Tue, 9 Nov 2004 22:53:47 +0100 Received: from warp (chateaudeau-4-82-225-176-25.fbx.proxad.net [82.225.176.25]) by postfix3-2.free.fr (Postfix) with SMTP id 5D04CC045; Tue, 9 Nov 2004 22:53:47 +0100 (CET) Message-ID: <000e01c4c6a6$fcbca9f0$19b0e152@warp> From: "Nicolas Cannasse" To: Cc: "caml-list" References: <00bc01c4c68b$4f1f6d70$19b0e152@warp> <1100036274.6138.10.camel@pelican.wigram> Subject: Re: [Caml-list] Native Module Linking Date: Tue, 9 Nov 2004 22:56:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Miltered: at nez-perce with ID 41913C6C.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at concorde with ID 41913C6B.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; cannasse:01 warplayer:01 caml-list:01 ocamldep:01 syntax:01 ocamlopt:01 ocamlc:01 cannasse:01 ....:98 activating:98 dependency:01 dependency:01 native:02 nicolas:02 nicolas:02 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on yquem.inria.fr X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.0 X-Spam-Level: > > 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