autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bad explanation in documentation on AC_CONFIG_FILES


From: Jason Dorje Short
Subject: bad explanation in documentation on AC_CONFIG_FILES
Date: Sun, 28 Mar 2004 01:18:30 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312 Debian/1.6-3

In the online documentation at

http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_chapter/autoconf_4.html#SEC20

is a section that says:


Commands:

Shell commands output literally into `config.status', and associated with a tag that the user can use to tell `config.status' which the commands to run. The commands are run each time a tag request is given to `config.status', typically each time the file `tag' is created.


This is unclear. The first sentence simply doesn't make sense. And the collective doesn't explain how the command is associated with a tag.


It seems to me that if you have

  AC_CONFIG_FILES([tag1 tag2 tag3], [commands])

then [commands] will be run after each file (tag) is created. If this is the case then the explanation just needs to be clarified, perhaps:

"Shell commands output literally into `config.status', and are associated with the tags that the user can use to tell `config.status' when to run the commands. The commands are run each time a tag request is given to `config.status', typically each time the file `tag' is created. If multiple tags are the commands will be associated with each one and may therefore be run multiple times. If this isn't what you want, you should move each tag and its commands into a separate AC_CONFIG_FOOS line so that the commands are not duplicated."

jason




reply via email to

[Prev in Thread] Current Thread [Next in Thread]