From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id TAA32530; Sun, 5 Sep 2004 19:15:19 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f 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 TAA32206 for ; Sun, 5 Sep 2004 19:15:17 +0200 (MET DST) Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net [203.16.214.203]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id i85HFFYa007225 for ; Sun, 5 Sep 2004 19:15:16 +0200 Received: from [192.168.1.200] (ppp210-32.lns2.syd3.internode.on.net [203.122.210.32]) by smtp3.adl2.internode.on.net (8.12.9/8.12.9) with ESMTP id i85HFCHY025114; Mon, 6 Sep 2004 02:45:13 +0930 (CST) Subject: Re: [Caml-list] Announcing the OMake build system version 0.9.1 From: skaller Reply-To: skaller@users.sourceforge.net To: "chris.danx" Cc: "Marcin 'Qrczak' Kowalczyk" , caml-list In-Reply-To: <413B3455.7020905@ntlworld.com> References: <4139ECD3.1050708@cs.caltech.edu> <001e01c492a6$872c7280$19b0e152@warp> <413A0921.7030607@ntlworld.com> <413A1E89.10806@libertysurf.fr> <1094361655.3352.476.camel@pelican.wigram> <87hdqc3kfr.fsf@qrnik.zagroda> <413B279C.3020304@ntlworld.com> <874qmc221f.fsf@qrnik.zagroda> <413B3455.7020905@ntlworld.com> Content-Type: text/plain Message-Id: <1094404512.3352.762.camel@pelican.wigram> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) Date: 06 Sep 2004 03:15:12 +1000 Content-Transfer-Encoding: 7bit X-Miltered: at nez-perce with ID 413B49A3.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 sourceforge:01 2004:99 44,:01 client's:99 python:01 python:01 autoconf:01 9660:01 glebe:01 chris:01 nsw:01 snail:02 unix:02 encoded:02 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk On Mon, 2004-09-06 at 01:44, chris.danx wrote: > > But how does it know it? How to specify that in a different way than > > for make? > > Isn't that information encoded in the source files already? The tool > extracts this information and uses it in the build process. Not quite -- the build rules have to be encoded, yes. However the encoding is as executable code, so whilst technically you're right it is extracted and 'used' by the build process, from the client's viewpoint it is simply executed. The build tool itself is a small Python script which calls functions from a Python library, and the user can enhance the processing in Python embedded in the source being read -- so the integration is fairly seamless. Contrast to autoconf, make, cake, imake ... :) In theory, these tools are also well integrated by the Unix OS and shell -- but I find Python script better (Perl would no doubt be good too). -- 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 ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners