Re: Libtool convenience library dependence check

[Andre Caldas]

> > I am using --disable-dependency-tracking as a configure option to 
> > avoid this problem. What kind of dependency can I expect to fail with 
> > this?
>
>
> If you edit a source file and add or remove a header file inclusion, 
> then make will not notice the change so it may produce bad results. If 
> you are using a distributed package, then the Makefile should include 
> the existing dependency information within itself.  If you bootstrapped 
> from scratch, then there may be not header dependency information at all.

Does it means that some prog.o will only be tested against some 
prog.cpp? All the other dependencies would be ignored... (or not even that?)

> This is actually an Automake issue rather than an Autoconf issue since 
> Automake is the one which adds the --disable-dependency-tracking option.

> You would usually only use --disable-dependency-tracking if you are 
> using some obscure proprietary compiler and it misbehaves while 
> compiling the package.

Definetely not my case ;-)
So, I suppose I should not use this. Thanks for the help.


Anyway, my initial problem is still there: "make install" will recompile 
every .cpp file in a convenience library even if no file (in the whole 
package) was edited! Can I call libtool a "obscure linker"?


Andre Caldas.