view finch/libgnt/autogen.sh @ 31072:3fad1d9e0bc3

Quote the path for the windows "run at startup" registry key. The only reason it ever worked like it was is that MS apparently has some wacky fallbacks that makes it find stuff in the Program Files folder when it sees a directory called "Program". Thanks to Christian Lange for noticing and tracking down the problem. Fixes #12781
author Daniel Atallah <daniel.atallah@gmail.com>
date Tue, 26 Oct 2010 18:52:56 +0000
parents 0e3a8505ebbe
children
line wrap: on
line source

#!/bin/sh

(libtoolize --version) < /dev/null > /dev/null 2>&1 || {
	echo;
	echo "You must have libtool installed to compile LibGNT";
	echo;
	exit;
}

(automake --version) < /dev/null > /dev/null 2>&1 || {
	echo;
	echo "You must have automake installed to compile LibGNT";
	echo;
	exit;
}

(autoconf --version) < /dev/null > /dev/null 2>&1 || {
	echo;
	echo "You must have autoconf installed to compile LibGNT";
	echo;
	exit;
}

echo "Generating configuration files for LibGNT, please wait...."
echo;

echo "Running libtoolize, please ignore non-fatal messages...."
echo n | libtoolize --copy --force || exit;

# Add other directories to this list if people continue to experience
# brokennesses ...  Obviously the real answer is for them to fix it
# themselves, but for Luke's sake we have this.
for dir in "/usr/local/share/aclocal" \
           "/opt/gnome-1.4/share/aclocal"
do
	if test -d $dir ; then
		ACLOCAL_FLAGS="$ACLOCAL_FLAGS -I $dir"
	fi
done

libtoolize -c -f --automake
aclocal $ACLOCAL_FLAGS || exit;
autoheader || exit;
automake --add-missing --copy;
autoconf || exit;
automake || exit;
./configure $@