On 03/10/2010 01:35 PM, TJ Yang wrote: > By default "./configure " will proceed to run itself and collect all > the system information. > > I am thinking of writing my own configure.ac to generate configure to split out > the content of "--help" or shoowing a usage message when there is no > argument provided. Why? That violates the GNU Coding Standards - many developers have come to expect configure to work without arguments, and your package would be broken in their eyes. > > Following code in configure.ac doesn't exit out right away when I type > in "./configure" > > MYARGS=2 > if test $# ne $MYARGS If you _absolutely_ must access $@ (or $*, $#), then your code to do so must occur immediately after AC_INIT: http://www.gnu.org/software/autoconf/manual/autoconf.html#Initializing-configure > then > echo "Need one argument at least.\n" > exit 0 Please don't. If you are going to make configure exit without completing, then at least exit with a non-zero status. -- Eric Blake eblake@xxxxxxxxxx +1-801-349-2682 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
