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 OAA27127 for caml-redistribution@pauillac.inria.fr; Fri, 25 Feb 2000 14:19:52 +0100 (MET) Resent-Message-Id: <200002251319.OAA27127@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 NAA19082 for ; Fri, 25 Feb 2000 13:29:21 +0100 (MET) Received: from sunhelmet.informatik.uni-tuebingen.de (sunhelmet.Informatik.Uni-Tuebingen.De [134.2.11.6]) by nez-perce.inria.fr (8.8.7/8.8.7) with ESMTP id NAA28801 for ; Fri, 25 Feb 2000 13:29:21 +0100 (MET) Received: (from pfitzen@localhost) by sunhelmet.informatik.uni-tuebingen.de (8.9.1a/8.9.1) id NAA07017 for caml-list@inria.fr; Fri, 25 Feb 2000 13:29:19 +0100 (MET) Date: Fri, 25 Feb 2000 13:29:19 +0100 (MET) From: Juergen Pfitzenmaier Message-Id: <200002251229.NAA07017@sunhelmet.informatik.uni-tuebingen.de> To: caml-list@inria.fr Subject: Re: Portability of applications written in OCAML: C stuff Resent-From: weis@pauillac.inria.fr Resent-Date: Fri, 25 Feb 2000 14:19:52 +0100 Resent-To: caml-redistribution@pauillac.inria.fr Max Skaller wrote on Wed, 23 Feb 2000 10:43:46 +1100 > 1. DO NOT USE A FILE CALLED 'config.h' .... > do NOT use generic names on the assumption your code will > be built with your Makefile in a separate directory. I have seen some big projects (> 100 MB code) and several smaller ones. In each of them people had to fight with the configuration. They all settled for what seems to be the least pain: built and distribute (!) in small blocks; keep each block in its own directory; use the same general frame for each block if possible (yes: use the name config.h over and over again). Even if its leading away from OCaml: I think that your real problem is with "make" and its way of building project. Look for "configuration management" and "make replacement" on the net. pfitzen