From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: *** X-Spam-Status: No, score=3.0 required=5.0 tests=AWL,DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST,NO_REAL_NAME,SPF_NEUTRAL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id A435FBC6C for ; Thu, 21 Jun 2007 21:33:31 +0200 (CEST) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id l5LJXUEJ032629 for ; Thu, 21 Jun 2007 21:33:31 +0200 Received: from vms125.mailsrvcs.net ([192.168.1.2]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JK00034H3NDYXMC@vms044.mailsrvcs.net> for caml-list@yquem.inria.fr; Thu, 21 Jun 2007 14:33:15 -0500 (CDT) Received: from 66.212.151.230 ([66.212.151.230]) by vms125.mailsrvcs.net (Verizon Webmail) with HTTP; Thu, 21 Jun 2007 14:33:13 -0500 (CDT) Date: Thu, 21 Jun 2007 14:33:13 -0500 (CDT) From: Subject: RE: windows and C libs X-Originating-IP: [66.212.151.230] To: caml-list@yquem.inria.fr Message-id: <21533682.3195491182454393783.JavaMail.root@vms125.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-Miltered: at concorde with ID 467AD28A.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; libs:01 lib:01 ocaml:01 ocamllib:01 ocamllib:01 stublibs:01 libpcre:01 lib:01 dllpcre:01 toolchain:01 sdk:01 polluting:01 dll's:01 verizon:98 msvc:01 > > Do you mean .lib/.dll files of some specific OCaml library? They > > usually go to %OCAMLLIB% and %OCAMLLIB%\stublibs respectively. What's > > wrong with it? > > No, I mean C library files -- e.g. where should the C-pcre libraries > (libpcre.lib, dllpcre.dll) go? In the MSVC toolchain, you can add the paths to your LIB and INCLUDE and PATH environment variables, or just drop them in the SDK directories if you don't mind polluting that. DLL's can either go in the . directory, which is the first place checked, or somewhere in the path.