From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: weis Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id SAA17309 for caml-redistribution@pauillac.inria.fr; Thu, 24 Feb 2000 18:48:09 +0100 (MET) Resent-Message-Id: <200002241748.SAA17309@pauillac.inria.fr> Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id QAA01455 for ; Thu, 24 Feb 2000 16:04:29 +0100 (MET) Received: from smarthost.microsoft.com ([131.107.3.106]) by nez-perce.inria.fr (8.8.7/8.8.7) with ESMTP id QAA24488 for ; Thu, 24 Feb 2000 16:04:26 +0100 (MET) Received: from ALAN-SCHM1P ([157.58.56.86]) by smarthost.microsoft.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2651.58) id 1T7FNK1W; Thu, 24 Feb 2000 07:04:21 -0800 Received: by alan-schm1p (sSMTP sendmail emulation); Thu, 24 Feb 2000 15:04:32 +0000 From: Alan Schmitt Date: Thu, 24 Feb 2000 15:04:32 +0000 To: OCAML Subject: Re: Portability of applications written in OCAML: C stuff Message-ID: <20000224150432.A9997@alan-schm1p.dns.microsoft.com> Mail-Followup-To: OCAML References: <200002231831.TAA11195@miss.wu-wien.ac.at> <38B49DBD.8DCBB87A@in.ot.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38B49DBD.8DCBB87A@in.ot.com.au>; from maxs@in.ot.com.au on Thu, Feb 24, 2000 at 01:55:57PM +1100 Organization: INRIA Rocquencourt Resent-From: weis@pauillac.inria.fr Resent-Date: Thu, 24 Feb 2000 18:48:09 +0100 Resent-To: caml-redistribution@pauillac.inria.fr .. >In particular, while my product is currently Unix only, the build >process >must work under Windows too, which rules out make, autoconf, and other >such silliness. :-) I gather this rules out using a compiler too ... ;-) In particular, when you say "must work under windows", do you mean out of the box window, or one with some tools installed (ocaml, python, cygwin thus bash, make ...) > pcre cannot build without config.h, and neither can mlgtk. >So there is a conflict, since both require a file called 'config.h'. I have many "config.h" in many source distributions in my /usr/src directory. I have never had such a problem. Actually, most of the time, to build an application you don't need to build the library. You actually require that it is there (and the nice thing is you can make your ./configure check for it). Librairies and include files are installed in some canonical places which can be looked up, or non-canonical which can be explicitely given to the installation script. >> > PLEASE use filenames that are specialised to your package, >> > do NOT use generic names on the assumption your code will >> > be built with your Makefile in a separate directory. >> >> This is impossible. > > It is not impossible to try. True, but since there is a nice mechanism to deal with this (ie Makefile and directories), is this really worth it ? Do you think we should adopt the java convention for naming ? This would be a pain ... Alan Schmitt -- The hacker: someone who figured things out and made something cool happen.