Tom Tromey <[EMAIL PROTECTED]> writes:
> >> 1. I can't get automake to read a dynamically created AC_OUTPUT
>...
> Yes, automake needs a static AC_OUTPUT list. Automake uses the
> argument to AC_OUTPUT to determine which Makefile.am's to scan.
>
> My suggestion: keep AC_OUTPUT static, and use dynamic SUBDIRS to
> decide which directories not to build.
The list of available packages is used in other places, eg. when
creating Javadoc information and jar distributions. Having it in both
a variable definition and the static AC_OUTPUT creates some
uneccessary maintenance. It would be a welcome change to be able
execute automake on a specific Makefile.am file. This could be done
when running the configure script.
> >> 2. The extension semantics does not enable me to use features of GNU
> >> Make like conditional statements, useful when not all compilers
>...
>
> Yes, automake does not allow this either. One goal of automake is to
> produce portable Makefiles. GNU make conditionals are not portable.
My naive dependency solution uses the ability of (GNU?) make to
depend on makefiles that are generated. These then contain the
required dependency information for the file in question (and are
generated by Jikes and gcj). The problem is when someone types `make
clean', in that case these auxiliary dependency files should be
cleaned and not recreated.
Before I start looking through the Automake sources, how is the
dependency tracking done in automake with gcc?
Yours,
Kai-Peter
