From: David.Mentre@irisa.fr (David Mentré)
To: Markus Mottl <mottl@miss.wu-wien.ac.at>
Cc: caml-list@inria.fr (OCAML)
Subject: Recursive Makefile (was: Re: OCaml makefile template comments)
Date: 25 Nov 1999 13:38:57 +0100 [thread overview]
Message-ID: <wd866yqoie6.fsf@parate.irisa.fr> (raw)
In-Reply-To: Markus Mottl's message of "Wed, 24 Nov 1999 21:49:50 +0100 (MET)"
Markus Mottl <mottl@miss.wu-wien.ac.at> writes:
> Is there a particular reason for objecting to recursive makefiles?
<religious-war>
I think you should read:
Recursive Make Considered Harmful (Peter Miller)
http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html
and *make your own opinion*. I've made mine.
</religious-war>
Anyway, thanks for your pointer. I'll take a look at it.
Best regards,
d.
--
David.Mentre@irisa.fr -- http://www.irisa.fr/prive/dmentre/
Opinions expressed here are only mine.
next prev parent reply other threads:[~1999-11-25 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-24 10:12 OCaml makefile template comments David Mentré
1999-11-24 20:49 ` Markus Mottl
1999-11-25 12:38 ` David Mentré [this message]
2000-01-09 0:22 ` Porting OCaml to A Custom OS Ravi Chamarty
2000-01-10 13:14 ` Xavier Leroy
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=wd866yqoie6.fsf@parate.irisa.fr \
--to=david.mentre@irisa.fr \
--cc=caml-list@inria.fr \
--cc=mottl@miss.wu-wien.ac.at \
/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).