Re: amtraces

[Akim Demaille <akim at epita dot fr>]

"Derek R. Price" <derek.price@openavenue.com> writes:

> Ok, I have amtraces code that slurps in almost all the information that
> scan_one_autoconf_file used to.  Unfortuantely I hit a minor snag:

We are probably working on the same things.  Please, show some code so
that we don't duplicate.

> Since _all_ AC_SUBSTs are being processed now, at least one instance
> where Automake was allowing for user override is now broken.
> 
> The case in question is the DEFAULT_INCLUDES variable being substituted
> in as part of DEFS.  

I don't understand :(

> Since Automake still asumes that a call to AC_SUBST(DEFS) is always
> user-requested and that a user request overrides the version of DEFS
> from comp-vars.am, DEFAULT_INCLUDES is no longer being set.
> 
> Since counting the AC_SUBST calls would be painful (each macro would
> have a different user count threshold and this could be variable), I'm
> thinking that the best solution is to define an AM_DEFS variable
> (modeled after AM_CPPFLAGS & AM_CFLAGS) and make it part of the COMPILE
> variable, then subst the old DEFAULT_INCLUDES value into that.
> 
> Is this the correct approach?

I really don't understand what you are talking about...  What is
DEFAULT_INCLUDES, how does it work?