This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: automake and AC_CONFIG_FILES($foo)
- From: Akim Demaille <akim at epita dot fr>
- To: Harlan Stenn <Harlan dot Stenn at pfcs dot com>
- Cc: automake at gnu dot org
- Date: 18 Apr 2002 12:19:30 +0200
- Subject: Re: automake and AC_CONFIG_FILES($foo)
- References: <41983.1018995617@dog.pfcs.com>
| autoconf handles AC_CONFIG_FILES($foo) properly.
But I should say it is not recommended! The documentation asks for
literals whenever it is possible.
| A plain invocation of "automake" rightly complains that it has no idea what
| it needs to look at, but running "automake (some list of Makefiles)"
| produces:
|
| configure.ac: 23: required file `./$foo.in' not found
|
| which seems wrong. If automake is called with explicit filename arguments
| it should ignore (or not complain) about variables in AC_CONFIG_FILES.
What is this $foo? Don't you need to EXTRA_DIST it somewhere? I'm
asking the question because precisely, if you move to
case $foo in
bar) AC_CONFIG_FILES(bar) ;;
foo) AC_CONFIG_FILES(foo) ;;
baz) AC_CONFIG_FILES(baz) ;;
esac
is what Autoconf recommends, and it would solve more of your problems,
wouldn't it?
I _insist_, I'm asking you to change your code: I'm (i) asking for
details to understand your needs, and (ii) _suggesting_ an alternative.