From: Markus Mottl <mottl@miss.wu-wien.ac.at>
To: David.Mentre@irisa.fr (David Mentré)
Cc: caml-list@inria.fr (OCAML)
Subject: Re: OCaml makefile template comments
Date: Wed, 24 Nov 1999 21:49:50 +0100 (MET) [thread overview]
Message-ID: <199911242049.VAA06574@miss.wu-wien.ac.at> (raw)
In-Reply-To: <wd8ogckqjuw.fsf@parate.irisa.fr> from "David =?iso-8859-1?q?Mentré?=" at Nov 24, 99 11:12:07 am
> Does anybody know a good makefile model to compile in subdirs
> (without recursive makefile) for OCaml?
Is there a particular reason for objecting to recursive makefiles?
Actually, projects that are spread over several directories have always
been a bit awkward to handle with the traditional "make". The easiest
solution is in most cases to have a specialized makefile in each directory,
which possibly makes use of some "meta-makefile".
I am not sure whether you have tried "OcamlMakefile" before (it strongly
relies on recursive invocation), but it has so far been appropriate for
just about any project I have undertaken. In general, the specialized
makefiles only require a few (=5-10) lines of code.
Here an example from the distribution:
---------------------------------------------------------------------------
OCAMLMAKEFILE = ../OcamlMakefile
SOURCES = test_impl.c test.idl parser.mly lexer.mll calc.ml
RESULT = calc
THREADS = yes
-include $(OCAMLMAKEFILE)
---------------------------------------------------------------------------
For more infos, see:
http://miss.wu-wien.ac.at/~mottl/ocaml_sources/intro.html
Regards,
Markus
--
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl
next prev parent reply other threads:[~1999-11-24 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-24 10:12 David Mentré
1999-11-24 20:49 ` Markus Mottl [this message]
1999-11-25 12:38 ` Recursive Makefile (was: Re: OCaml makefile template comments) David Mentré
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=199911242049.VAA06574@miss.wu-wien.ac.at \
--to=mottl@miss.wu-wien.ac.at \
--cc=David.Mentre@irisa.fr \
--cc=caml-list@inria.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