caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Brown <caml-list@davidb.org>
To: skaller <skaller@ozemail.com.au>
Cc: sylvain.le-gall@polytechnique.org,
	Nicolas Cannasse <warplayer@free.fr>,
	David Brown <caml-list@davidb.org>,
	Martin Jambon <martin_jambon@emailuser.net>,
	caml-list@inria.fr
Subject: Re: [Caml-list] Building large and portable projects
Date: Sat, 22 Nov 2003 09:13:39 -0800	[thread overview]
Message-ID: <20031122171339.GB15144@davidb.org> (raw)
In-Reply-To: <1069431167.5426.45.camel@pelican>

On Sat, Nov 22, 2003 at 03:12:48AM +1100, skaller wrote:

> First observe that building a system
> is a process where it is not always
> possible to determine the full sequence
> of commands in advance. Sometimes,
> you have to perform some action before
> you can decide what to do next.

Make doesn't try to determine everything in advance.  Well, sorta :-)
It does try to figure everything out in advance, and then sometimes
looks to see if that needs to change.  It makes it work in a few
situations where it wouldn't before.

A while back, I build something like ocamake that let you specify a
command like:

  myomake -o target a b c

This would compile modules a, b, and c, and any that they depended on.
They would be linked in an order that would link.  If you need more
control, you can specify additional modules on the command line.  This
kind of tool is useful for many projects.

Once I discovered not to try and figure everything out in advance, the
tool not only became easier to write, but possible.

Once other stuff is brought in (C, literate programming), the
specification needs to be more complex.

Dave

-------------------
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


  parent reply	other threads:[~2003-11-22 17:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 18:47 Martin Jambon
2003-11-20 19:56 ` sylvain.le-gall
2003-11-21  1:45   ` Nicolas Cannasse
2003-11-21  5:25     ` David Brown
2003-11-21  5:48       ` Nicolas Cannasse
2003-11-21  6:45         ` David Brown
2003-11-21  6:49         ` sylvain.le-gall
2003-11-21 16:12           ` skaller
2003-11-21 17:53             ` Eric Dahlman
2003-11-22 14:45               ` skaller
2003-11-21 19:04             ` sylvain.le-gall
2003-11-22 14:34               ` skaller
2003-11-22 18:50                 ` sylvain.le-gall
2003-11-22 14:32             ` Martin Berger
2003-11-22 14:55               ` skaller
2003-11-22 17:08             ` David Brown
2003-11-22 16:48               ` skaller
2003-11-23  3:25               ` Nicolas Cannasse
2003-11-23  4:29                 ` David Brown
2003-11-23 17:21                 ` skaller
2003-11-22 17:13             ` David Brown [this message]
2003-11-24 18:02             ` Ken Rose
2003-11-24 19:04               ` Christian Lindig
2003-11-21 16:32           ` Martin Jambon
2003-11-21 18:57             ` sylvain.le-gall
2003-11-21  9:14       ` Christian Lindig
2003-11-21  9:28 ` Richard Jones
2003-11-21 15:35 ` skaller
2003-11-21 17:05 ` Jason Hickey
2003-11-21 18:55   ` sylvain.le-gall
2003-11-21 19:30     ` [Caml-list] Omake [Was: Building large and portable projects] Aleksey Nogin
2003-11-21 20:39       ` Damien
2003-11-22  3:30         ` Aleksey Nogin
2003-11-21 23:48       ` sylvain.le-gall
2003-11-22  1:32         ` Nicolas Cannasse
2003-11-22  3:51         ` Aleksey Nogin
2003-11-28 16:29   ` [Caml-list] Building large and portable projects David Brown

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=20031122171339.GB15144@davidb.org \
    --to=caml-list@davidb.org \
    --cc=caml-list@inria.fr \
    --cc=martin_jambon@emailuser.net \
    --cc=skaller@ozemail.com.au \
    --cc=sylvain.le-gall@polytechnique.org \
    --cc=warplayer@free.fr \
    /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).