On Tuesday 14 March 2006 11:54, david wrote:
> Hi Joerg,
> I sent a list of all know packages to Andreas so he may be able to find
> what is missing. I would have posted my reply to the list but..... you
> know.
>
> I'm trying to figure out the configure/make process a little more.
> It currently works on my machine but my understanding has some holes
> (large ones)
>
> aclocal runs first
> It reads from configure.ac (doco says configure.in)
> And writes to aclocal.m4 (and autom4te.cache)
I found a sentence like configure.in (and sometimes configure.ac) in one of
the dokus.
> automake runs next
> I can't tell where it reads from but I guess aclocal.m4
> (It may also read from configure.ac)
> It writes a makefile.in for each source directory
>
> autoconf then runs
> I guess it must read from all the makefile.in in each directory
> And generate the configure script.
>
> So the only file that appears to have manual intervention is
> configure.ac but from your note to Andreas you just commented out a line
> in Makefile.am which didn't make it into my description above. I had
> assumed that configure.ac would be the place to add all the new
> dependancies. Perhaps not? Any advice?
As of my understanding configure.ac is the place to out the dependencies, but
if the compile process doesn't need the libraries you don't need the
dependency. That was what I was thinking ;-) I hope it works. Since I can't
really test it here. (I have all the gdal-libs installed).
-
Joerg
--
This message was part of the gpsdrive mailinglist
unsubscribing can be done by sending a mail containing a body of:
-quote--
unsubscribe gpsdrive
-unquote--
to majordomo-ahljRfkWE0EwtzFM8z8+AfP6llvjuJOh@xxxxxxxxxxxxxxxx
|
