From: skaller <skaller@users.sourceforge.net>
To: "chris.danx" <chris.danx@ntlworld.com>
Cc: "Marcin 'Qrczak' Kowalczyk" <qrczak@knm.org.pl>,
caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Announcing the OMake build system version 0.9.1
Date: 06 Sep 2004 03:15:12 +1000 [thread overview]
Message-ID: <1094404512.3352.762.camel@pelican.wigram> (raw)
In-Reply-To: <413B3455.7020905@ntlworld.com>
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
next prev parent reply other threads:[~2004-09-05 17:15 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 16:26 Jason Hickey
2004-09-04 17:42 ` Nicolas Cannasse
2004-09-04 18:27 ` chris.danx
2004-09-04 19:59 ` Matthieu Dubuget
2004-09-05 5:20 ` skaller
2004-09-05 13:20 ` David Brown
2004-09-05 14:31 ` skaller
2004-09-05 16:02 ` David Brown
2004-09-05 16:14 ` Nicolas Cannasse
2004-09-05 15:07 ` chris.danx
2004-09-05 15:53 ` skaller
2004-09-06 0:25 ` chris.danx
2004-09-06 8:17 ` skaller
2004-09-05 13:38 ` Marcin 'Qrczak' Kowalczyk
2004-09-05 14:50 ` chris.danx
2004-09-05 15:01 ` Marcin 'Qrczak' Kowalczyk
2004-09-05 15:44 ` chris.danx
2004-09-05 16:10 ` Marcin 'Qrczak' Kowalczyk
2004-09-05 17:38 ` skaller
2004-09-05 17:15 ` skaller [this message]
2004-09-05 16:11 ` skaller
2004-09-05 16:21 ` Marcin 'Qrczak' Kowalczyk
2004-09-05 19:09 ` skaller
2004-09-05 15:08 ` skaller
2004-09-05 15:38 ` Marcin 'Qrczak' Kowalczyk
2004-09-05 17:04 ` skaller
2004-09-05 18:45 ` Marcin 'Qrczak' Kowalczyk
2004-09-05 20:12 ` skaller
2004-09-05 21:30 ` Marcin 'Qrczak' Kowalczyk
2004-09-05 22:41 ` Brandon J. Van Every
2004-09-06 12:13 ` Marcin 'Qrczak' Kowalczyk
2004-09-05 16:09 ` David Brown
2004-09-05 18:31 ` skaller
2004-09-06 10:56 ` Andreas Rossberg
2004-09-06 15:51 ` skaller
2004-09-06 7:11 ` Christian Lindig
2004-09-06 12:20 ` Marcin 'Qrczak' Kowalczyk
2004-09-06 14:12 ` Christian Lindig
2004-09-06 1:06 ` Richard Jones
2004-09-06 1:50 ` Brandon J. Van Every
2004-09-06 9:09 ` skaller
2004-09-06 8:59 ` skaller
2004-09-04 23:58 ` Nicolas Cannasse
2004-09-05 1:18 ` james woodyatt
2004-09-05 1:26 ` [Caml-list] Perl Conjury (alternative to Unix make) james woodyatt
2004-09-05 2:03 ` [Caml-list] Announcing the OMake build system version 0.9.1 David Brown
2004-09-05 2:37 ` james woodyatt
2004-09-05 6:24 ` Nathaniel Gray
2004-09-05 20:38 ` Aleksey Nogin
2004-09-06 0:12 ` james woodyatt
2004-09-06 0:33 ` [Omake] " Aleksey Nogin
2004-09-06 3:54 ` Brian Hurt
2004-09-06 6:39 ` Jason Hickey
2004-09-06 8:10 ` james woodyatt
2004-09-06 7:50 ` [Omake] " Erik de Castro Lopo
2004-09-06 14:52 ` Brian Hurt
2004-09-06 17:20 ` skaller
2004-09-06 9:52 ` skaller
2004-09-06 15:10 ` Brian Hurt
2004-09-07 13:26 ` David Brown
2004-09-06 1:14 ` Brandon J. Van Every
2004-09-06 2:35 ` Jacques GARRIGUE
2004-09-06 9:38 ` skaller
2004-09-06 11:34 ` Jacques Garrigue
2004-09-06 16:28 ` skaller
2004-09-06 16:42 ` Christopher A. Watford
2004-09-06 16:59 ` Richard Jones
2004-09-07 2:21 ` Jacques GARRIGUE
2004-09-07 6:17 ` skaller
2004-09-07 8:24 ` Benjamin Geer
2004-09-07 13:35 ` David Brown
2004-09-06 7:51 ` Daniel Andor
2004-09-05 20:38 ` Aleksey Nogin
2004-09-05 22:57 ` Olivier Grisel
2004-09-06 0:17 ` Aleksey Nogin
2004-09-06 13:31 ` Olivier Grisel
2004-09-06 19:28 ` [Caml-list] Godi for OMake [Was: Announcing the OMake build system version 0.9.1] Aleksey Nogin
2004-09-06 20:18 ` Olivier Grisel
[not found] ` <41537DAE.1050601@cs.caltech.edu>
2004-09-24 13:50 ` Olivier Grisel
2004-09-24 18:37 ` [Caml-list] OCamlFind support in OMake [Was: Godi for OMake] Aleksey Nogin
2004-09-04 18:01 ` [Caml-list] Announcing the OMake build system version 0.9.1 Yaron Minsky
2004-09-05 1:38 ` Eray Ozkural
2004-09-05 6:12 ` Yamagata Yoriyuki
2004-09-05 12:48 ` Yaron Minsky
2004-09-05 20:39 ` Aleksey Nogin
2004-09-06 12:24 Jason Smith
2004-09-06 15:54 ` Christopher A. Watford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1094404512.3352.762.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=chris.danx@ntlworld.com \
--cc=qrczak@knm.org.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).