curl/ares/buildconf

#!/bin/sh

if test -z "$ACLOCAL_FLAGS"; then
  ACLOCAL_FLAGS="-I m4"
else
  ACLOCAL_FLAGS="$ACLOCAL_FLAGS -I m4"
fi

${LIBTOOLIZE:-libtoolize} --copy --automake --force
${ACLOCAL:-aclocal} $ACLOCAL_FLAGS
${AUTOHEADER:-autoheader}
${AUTOCONF:-autoconf}
${AUTOMAKE:-automake} --add-missing
when checked out from CVS, run this to generate the proper scripts 2004-04-11 02:32:41 -04:00			`#!/bin/sh`

When calling aclocal, user defined ACLOCAL_FLAGS will now precede ours. 2008-07-27 14:10:54 -04:00			`if test -z "$ACLOCAL_FLAGS"; then`
			`ACLOCAL_FLAGS="-I m4"`
			`else`
			`ACLOCAL_FLAGS="$ACLOCAL_FLAGS -I m4"`
			`fi`

Allow environment variables to override default autotools. 2005-04-12 20:32:33 -04:00			`${LIBTOOLIZE:-libtoolize} --copy --automake --force`
Use $ACLOCAL_FLAGS too, pointed out by Alexander Lazic 2006-01-06 17:07:51 -05:00			`${ACLOCAL:-aclocal} $ACLOCAL_FLAGS`
Allow environment variables to override default autotools. 2005-04-12 20:32:33 -04:00			`${AUTOHEADER:-autoheader}`
			`${AUTOCONF:-autoconf}`
			`${AUTOMAKE:-automake} --add-missing`