Re: Stopping aclocal from re-building

[David Knox]

Thanks Patrick,
Your suggestion appears to solve aclocal.m4 from getting overwritten. I 
didn't realize that adding macros to m4 is a bad practice but knowing 
what I've learned, I can see the problem.

I very much would like to stop autoconf from generating the rules to 
re-run aclocal, automake, and autoconf. I've noticed that if I specify 
the rules I want in my Makefile.am-s, then only those rules get 
generated. Is this the best way to turn of the generation of these 
re-generating rules?

thanks in advance --
-- dave

Patrick Welche wrote:

> On Sat, May 22, 2004 at 11:12:44AM -0600, David Knox wrote:
>  
>
> > I'm a newbie using autotools on a fairly small project. I've been able 
> > to get it to do most everything I want with the help of the macro 
> > archive and the great examples in it. I have one problem that is driving 
> > me nuts. I haven't figured out exactly what triggers this, but sometimes 
> > the build process will run aclocal. This over writes my old aclocal, 
> > which is a problem. When this happens, simply copy over the newly 
> > generated copy. I've scanned the list archives and read the online 
> > manual. I wasn't able to find anything specific to this question. Can 
> > some one give me a hint how to turn this behavior off?
> >    
>
> Does this mean that you are adding your own macros to aclocal.m4? Maybe
> you could try adding them to acinclude.m4 instead, or popping them in
> m4/yourownmacros.m4 with AC_CONFIG_MACRO_DIR([m4]) (depending on your
> version of autoconf) Then aclocal will fish them out and pop them into
> the new aclocal.m4.
>
> Cheers,
>
> Patrick
>
>
>