mapnik/configure

#!/bin/sh

set -eu

PYTHON=${PYTHON:-python}

# mapnik-settings.env is an optional file to store
# environment variables that should be used before
# running tests like PROJ_LIB, GDAL_DATA, and ICU_DATA
# These do not normally need to be set except when
# building against binary versions of dependencies like
# done via bootstrap.sh
if [[ -f mapnik-settings.env ]]; then
    echo "Inheriting from mapnik-settings.env"
    source mapnik-settings.env
fi

$PYTHON scons/scons.py --implicit-deps-changed configure "$@"
Use sh instead of bash for configure Not everywhere has bash installed or installs it to /bin/bash Given that there's no bash-specific features in configure, it makes sense to just use sh 2015-05-24 00:59:52 +02:00			`#!/bin/sh`
Add ./configure and MakeFile, simple wrappers around scons scripts 2011-02-04 23:29:10 +01:00
port #3759 to master 2017-09-10 17:19:04 +02:00			`set -eu`

Allow user to specify a python executable.¬ ¬ Fall back on `python`. Unlike the solution in PR #2395 this¬ puts all the responsibility for selecting the right python in the¬ case that "python" is Python 3 on the user. I've followed the lead¬ of the Python documentation Makefile. See http://hg.python.org/cpython/file/340d48347295/Doc/README.txt http://hg.python.org/cpython/file/340d48347295/Doc/Makefile Intent is that if your `python` is Python 2 everything works as before and that is your `python` is Python 3 but you have a `python2` you can specify that instead.¬ Conflicts: run_tests 2014-09-03 23:57:27 +02:00			`PYTHON=${PYTHON:-python}`

port #3759 to master 2017-09-10 17:19:04 +02:00			`# mapnik-settings.env is an optional file to store`
			`# environment variables that should be used before`
			`# running tests like PROJ_LIB, GDAL_DATA, and ICU_DATA`
			`# These do not normally need to be set except when`
			`# building against binary versions of dependencies like`
			`# done via bootstrap.sh`
			`if [[ -f mapnik-settings.env ]]; then`
			`echo "Inheriting from mapnik-settings.env"`
			`source mapnik-settings.env`
			`fi`

Allow user to specify a python executable.¬ ¬ Fall back on `python`. Unlike the solution in PR #2395 this¬ puts all the responsibility for selecting the right python in the¬ case that "python" is Python 3 on the user. I've followed the lead¬ of the Python documentation Makefile. See http://hg.python.org/cpython/file/340d48347295/Doc/README.txt http://hg.python.org/cpython/file/340d48347295/Doc/Makefile Intent is that if your `python` is Python 2 everything works as before and that is your `python` is Python 3 but you have a `python2` you can specify that instead.¬ Conflicts: run_tests 2014-09-03 23:57:27 +02:00			`$PYTHON scons/scons.py --implicit-deps-changed configure "$@"`