curl/ares/buildconf

#!/bin/sh

if test -z "$ACLOCAL_FLAGS"; then
  ACLOCAL_FLAGS="-I m4"
else
  ACLOCAL_FLAGS="$ACLOCAL_FLAGS -I m4"
fi
export ACLOCAL_FLAGS
echo "cares buildconf: using ACLOCAL_FLAGS: $ACLOCAL_FLAGS"

${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 06:32:41 +00:00			`#!/bin/sh`

When calling aclocal, user defined ACLOCAL_FLAGS will now precede ours. 2008-07-27 18:10:54 +00:00			`if test -z "$ACLOCAL_FLAGS"; then`
			`ACLOCAL_FLAGS="-I m4"`
			`else`
			`ACLOCAL_FLAGS="$ACLOCAL_FLAGS -I m4"`
			`fi`
for debugging purposes show ACLOCAL_FLAGS 2008-07-28 15:13:31 +00:00			`export ACLOCAL_FLAGS`
			`echo "cares buildconf: using ACLOCAL_FLAGS: $ACLOCAL_FLAGS"`
When calling aclocal, user defined ACLOCAL_FLAGS will now precede ours. 2008-07-27 18:10:54 +00:00
Allow environment variables to override default autotools. 2005-04-13 00:32:33 +00:00			`${LIBTOOLIZE:-libtoolize} --copy --automake --force`
Use $ACLOCAL_FLAGS too, pointed out by Alexander Lazic 2006-01-06 22:07:51 +00:00			`${ACLOCAL:-aclocal} $ACLOCAL_FLAGS`
Allow environment variables to override default autotools. 2005-04-13 00:32:33 +00:00			`${AUTOHEADER:-autoheader}`
			`${AUTOCONF:-autoconf}`
			`${AUTOMAKE:-automake} --add-missing`