Ralf Wildenhues wrote:
> > To me, it looks like AM_CPPFLAGS is empty by default. Automake's default
> > includes are in a separate variable called DEFAULT_INCLUDES.
>
> Only if you've used nostdinc (`info Automake "Program variables"'):
>
> | `AM_CPPFLAGS' <doc of AM_CPPFLAGS>
Then the doc of AM_CPPFLAGS is misunderstandable. What I've observed with
automake 1.10, is that after running "gnulib-tool --create-testdir ..."
- The generated Makefile.am has a line defining AM_CPPFLAGS to empty.
- The Makefile then has an empty AM_CPPFLAGS as well, and a variable
DEFAULT_INCLUDES that contains -I. and others.
- When I remove the line that defines AM_CPPFLAGS from Makefile.am, it
disappears also from the Makefile. This has no effect on the build.
> | The contents of this variable are passed to every compilation that
> | invokes the C preprocessor; it is a list of arguments to the
> | preprocessor. For instance, `-I' and `-D' options should be
> | listed here.
> |
> | Automake already provides some `-I' options automatically.
It will be less prone to misunderstandings if you change that last sentence to
"Automake already provides some `-I' options automatically, in a
separate variable that is also passed to every compilation that
invokes the C preprocessor."
Bruno
