Re: AC_CONFIG_FILES and chmod

[Bob Friesenhahn]

On Tue, 16 Jun 2009, Eric Blake wrote:
> You could use AC_CONFIG_COMMANDS and create a single tag that performs the
> chmod for all such files in a single process.  This is similar to the
> AC_CONFIG_COMMANDS tag created by automake for computing compilation
> dependencies all in one step.  However, there is no way to associate that
> tag with the tag for each file, and also remember that config.status can
> instantiate just one rather than every tag.  Thus, if the user builds just
> one file, they would have to independently also request the tag that runs
> the bulk chmod command.  So it may be safest after all to just keep with
> the current usage of one chmod command per file that needs it, even though
> that ends up with more typing in configure.ac and more processes during
> config.status.

I have not yet gotten AC_CONFIG_COMMANDS to work as expected.  By 
default config.status processes all of the files and it seems that the 
extra rules specified by AC_CONFIG_COMMANDS get used.  But if only one 
file gets re-generated (e.g. due to the source file being edited), 
then config.status does the substitutions but does not execute the 
command specified by AC_CONFIG_COMMANDS so the resulting file is not 
executable.

The documentation was not much help.

For example:

AC_CONFIG_COMMANDS([PerlMagick/PerlMagickCheck.sh.in],[chmod +x 
PerlMagick/PerlMagickCheck.sh])
AC_OUTPUT(PerlMagick/PerlMagickCheck.sh)

What am I missing?

Bob
--
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/