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 _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
