Re: autoconf/automake questions

[Federico Montesino Pouzols]

        I have found that newer releases of autoconf and automake
(from 2.5x and 1.6 on) handle dependencies (including .am and .in
files) more strictly, so the two problems you mention disappear when
using these autotools releases. With classic releases I would say it
is more reliable to use reconfig and configure. Anyway, if you just
want to do a quick compilation of an additional SOURCE, one can always
edit the Makefile :)

On Sun, Dec 29, 2002 at 11:58:57AM +0200, Albert Strasheim wrote:
> Hello,
> 
> I have some questions regarding the autoconf and automake configuration 
> of the Common C++ project, specifically the commoncpp2 CVS module.
> 
> Firstly, it seems that whenever one runs ./configure, everything is 
> rebuilt the next time you run make. This is probably a good policy in 
> general, but when one is working on files related to the build system 
> and you know that the configure options haven't changed, you might want 
> to turn this off. Which macro do I hack? :-)
> 
> Secondly, changes to Makefile.am doesn't seem to automatically trigger 
> the "rebuilding" of Makefile.in and Makefile, instead requiring that one 
> does a ./reconfig && ./configure, causing a complete rebuild as 
> described above.
> 
> This is quite annoying when you are adding files to a specific _SOURCES 
> target, and just want to rebuild just this one target with the 
> additional sources. How do I change this behaviour?
> 
> Happy holidays and all that. :-)
> 
> Cheers,
> 
> Albert
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp