From: David MENTRE <dmentre@linux-france.org>
To: Kenneth Knowles <kknowles@berkeley.edu>
Cc: Richard Jones <rich@annexia.org>, caml-list@inria.fr
Subject: Re: [Caml-list] Intelligent handling of dependencies in complex ocaml projects
Date: Thu, 15 Apr 2004 09:46:35 +0200 [thread overview]
Message-ID: <87oeptr8dg.fsf@linux-france.org> (raw)
In-Reply-To: <20040414153619.GA23982@tallman.kefka.frap.net> (Kenneth Knowles's message of "Wed, 14 Apr 2004 08:36:19 -0700")
Kenneth Knowles <kknowles@berkeley.edu> writes:
> I was thinking the same thing.
> http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html
>
> On Wed, Apr 14, 2004 at 04:18:53PM +0100, Richard Jones wrote:
>> Have you considered using a single non-recursive Makefile? Then you
>> can use ocamldep and a single .depend file to store the built
>> dependencies, and you can also be sure that your builds will be
>> correct.
Richard and Kenneth, are you refering to my post or Cezary's one?
In my specific case, I completely agree with Miller's point of view. The
only issue is that I'm using ocamldep to compile Gerd's ocamlrpcgen to
generate new ocaml source files to then reuse ocamldep to finally
compile my program. I cannot do that without two successive make
includes. That's said (1) I would much prefer a simpler solution and (2)
my Makefile is still a monolithic Makefile as per Miller suggestion.
Now, regarding Cezary issues, I though his main issue was that ocamldep
options where incompatible for different sub-directories. But maybe
ocamldep does not need that much options.
Yours,
d.
--
David Mentré <dmentre@linux-france.org>
-------------------
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
prev parent reply other threads:[~2004-04-15 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 12:30 Cezary Kaliszyk
2004-04-14 12:56 ` David MENTRE
2004-04-14 15:18 ` Richard Jones
2004-04-14 15:36 ` Kenneth Knowles
2004-04-15 7:46 ` David MENTRE [this message]
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=87oeptr8dg.fsf@linux-france.org \
--to=dmentre@linux-france.org \
--cc=caml-list@inria.fr \
--cc=kknowles@berkeley.edu \
--cc=rich@annexia.org \
/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).