From: Jean-Christophe Filliatre <filliatr@lri.fr>
To: skaller <skaller@users.sourceforge.net>
Cc: Guillaume Rousse <Guillaume.Rousse@inria.fr>,
caml-list@yquem.inria.fr, autoconf@gnu.org
Subject: Re: [Caml-list] managing ocaml dependencies
Date: Thu, 16 Nov 2006 20:01:17 +0100 [thread overview]
Message-ID: <17756.46461.9739.327852@serveur9-10.lri.fr> (raw)
In-Reply-To: <1163695632.20151.34.camel@rosella.wigram>
skaller writes:
> On Thu, 2006-11-16 at 15:20 +0100, Guillaume Rousse wrote:
>
> > They are two different strategies here, either generate them on
> > maintainer host and ship them in the distribution, either generate them
> > on user's host.
>
> There is no choice: it has to be done by the developer
> because sometimes the dependency is semantic, in particular
> when order of initialisation matters.
The link order and the modules dependencies are two different matters.
Typically, the Makefile contains the link order but dependencies can
indeed be generated automatically, even on the fly; with the possible
issues mentioned by Guillaume, though.
Regarding the latter, I use the following typical Makefile for my
projects: http://www.lri.fr/~filliatr/ftp/ocaml/misc/Makefile.in
(together with http://www.lri.fr/~filliatr/ftp/ocaml/misc/configure.in)
and I ship the .depend file within the distributions.
(I don't include Makefiles; I use a single Makefile at the top
directory) But having the dependencies built by the ./configure seems
to be a good solution...
--
Jean-Christophe
next prev parent reply other threads:[~2006-11-16 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 14:20 Guillaume Rousse
2006-11-16 16:47 ` [Caml-list] " skaller
2006-11-16 19:01 ` Jean-Christophe Filliatre [this message]
2006-11-16 21:43 ` Nicolas Pouillard
2006-11-17 0:36 ` skaller
2006-11-16 21:21 ` Ralf Wildenhues
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=17756.46461.9739.327852@serveur9-10.lri.fr \
--to=filliatr@lri.fr \
--cc=Guillaume.Rousse@inria.fr \
--cc=autoconf@gnu.org \
--cc=caml-list@yquem.inria.fr \
--cc=skaller@users.sourceforge.net \
/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