From: Christian Lindig <lindig@cs.uni-sb.de>
To: "Marcin 'Qrczak' Kowalczyk" <qrczak@knm.org.pl>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Announcing the OMake build system version 0.9.1
Date: Mon, 6 Sep 2004 09:11:55 +0200 [thread overview]
Message-ID: <08C9709F-FFD4-11D8-97B9-000A95CB833C@cs.uni-sb.de> (raw)
In-Reply-To: <87hdqc3kfr.fsf@qrnik.zagroda>
On Sep 5, 2004, at 3:38 PM, Marcin 'Qrczak' Kowalczyk wrote:
> It would be interesting to invent some alternative paradigm, but I've
> never seen one.
Here are the paradigms for build systems that I know:
Make - uses rules to specify the dependency tree, walks the dependency
tree, analyzes the file system, and builds files concurrently (hence,
no planning in advance)
Vesta - specifies the build procedure in a functional language and
evaluates the procedure for building. No concept of updating like in
Make - all builds are complete in concept; efficiency comes from
caching intermediate results and hence the evaluator knows that it does
not have to rebuild everything. The Vesta system observes dependencies
by observing the tools that are run during the build process: which
files are read and written. Very powerful but is more an environment
than a tool.
Jam - like Make, but has procedural abstraction: a program is
evaluated to build up the dependency tree. Unlike Make, clean
separation of phases: analyzes the file system, makes a plan, and
executes it. Hence, no checking the file system while executing the
plan. Similar tools: Cons, SCons.
You can find papers here:
http://www.research.compaq.com/SRC/vesta/pubs/pldi-00-04-20.pdf
http://www.dsmit.com/cons/
http://www.perforce.com/jam/jam.html
http://www.perforce.com/jam/jam.html
-- Christian
--
http://www.st.cs.uni-sb.de/~lindig/
-------------------
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-06 7:17 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
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 [this message]
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=08C9709F-FFD4-11D8-97B9-000A95CB833C@cs.uni-sb.de \
--to=lindig@cs.uni-sb.de \
--cc=caml-list@inria.fr \
--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