libexpat/expat/buildconf.sh
Greg Stein a13d856e8f * Switch to a single, top-level Makefile (simplification, consistency)
* use libtool to compile/link all programs
* remove */Makefile.in and remove them from configure
* remove autom4te.cache after running autoconf
* remove .o from the FILEMAP logic in configure and the Make system;
  provides more flexibility in the Makefile to use it
* for VPATH builds: create the build subdirs by running
  "make mkdir-init" from the configure script
* adjust .cvsignore files to account for presence of .libs now
2001-12-07 10:19:31 +00:00

49 lines
1.2 KiB
Bash
Executable File

#! /bin/sh
#
# Create the libtool helper files
#
echo "Copying libtool helper files ..."
#
# find libtoolize, or glibtoolize on MacOS X
#
libtoolize=`conftools/PrintPath glibtoolize libtoolize`
if [ "x$libtoolize" = "x" ]; then
echo "libtoolize not found in path"
exit 1
fi
#
# --force to ensure that we replace with current files
# --copy to avoid symlinks; we want originals for the distro
# --automake to make it shut up about "things to do"
#
(cd conftools/; rm -f ltmain.sh ltconfig)
$libtoolize --force --copy --automake
ltpath=`dirname $libtoolize`
ltfile=`cd $ltpath/../share/aclocal ; pwd`/libtool.m4
cp $ltfile conftools/libtool.m4
### for a little while... remove stray aclocal.m4 files from
### developers' working copies. we no longer use it. (nothing else
### will remove it, and leaving it creates big problems)
rm -f aclocal.m4
#
# Generate the autoconf header template (config.h.in) and ./configure
#
echo "Creating config.h.in ..."
autoheader
echo "Creating configure ..."
### do some work to toss config.cache?
autoconf
# toss this; it gets created by autoconf on some systems
rm -rf autom4te.cache
# exit with the right value, so any calling script can continue
exit 0