rust/configure

#!/bin/sh

script="$(dirname $0)"/src/bootstrap/configure.py

try() {
    cmd=$1
    shift
    T=$($cmd --version 2>/dev/null)
    if [ $? -eq 0 ]; then
        exec $cmd "$script" "$@"
    fi
}

try python2.7 "$@"
try python27 "$@"
try python2 "$@"
exec python $script "$@"
configure: Rename --enable-debug to --enable-debug-assertions 2015-04-08 20:17:46 +00:00			`#!/bin/sh`
Beginning of build-system upgrade. 2011-03-16 16:17:32 +00:00
rustbuild: Rewrite the configure script in Python This commit rewrites our ancient `./configure` script from shell into Python. The impetus for this change is to remove `config.mk` which is just a vestige of the old makefile build system at this point. Instead all configuration is now solely done through `config.toml`. The python script allows us to more flexibly program (aka we can use loops easily) and create a `config.toml` which is based off `config.toml.example`. This way we can preserve comments and munge various values as we see fit. It is intended that the configure script here is a drop-in replacement for the previous configure script, no functional change is intended. Also note that the rationale for this is also because our build system requires Python, so having a python script a bit earlier shouldn't cause too many problems. Closes #40730 2017-08-26 22:01:48 +00:00			`script="$(dirname $0)"/src/bootstrap/configure.py`
Add Illumos support 2016-01-21 16:30:22 +00:00
rustbuild: Rewrite the configure script in Python This commit rewrites our ancient `./configure` script from shell into Python. The impetus for this change is to remove `config.mk` which is just a vestige of the old makefile build system at this point. Instead all configuration is now solely done through `config.toml`. The python script allows us to more flexibly program (aka we can use loops easily) and create a `config.toml` which is based off `config.toml.example`. This way we can preserve comments and munge various values as we see fit. It is intended that the configure script here is a drop-in replacement for the previous configure script, no functional change is intended. Also note that the rationale for this is also because our build system requires Python, so having a python script a bit earlier shouldn't cause too many problems. Closes #40730 2017-08-26 22:01:48 +00:00			`try() {`
			`cmd=$1`
Teach configure to search for multiple commands-with-similar-names. Add NaturalDocs (vs. naturaldocs). 2012-01-19 21:08:01 +00:00			`shift`
rustbuild: Rewrite the configure script in Python This commit rewrites our ancient `./configure` script from shell into Python. The impetus for this change is to remove `config.mk` which is just a vestige of the old makefile build system at this point. Instead all configuration is now solely done through `config.toml`. The python script allows us to more flexibly program (aka we can use loops easily) and create a `config.toml` which is based off `config.toml.example`. This way we can preserve comments and munge various values as we see fit. It is intended that the configure script here is a drop-in replacement for the previous configure script, no functional change is intended. Also note that the rationale for this is also because our build system requires Python, so having a python script a bit earlier shouldn't cause too many problems. Closes #40730 2017-08-26 22:01:48 +00:00			`T=$($cmd --version 2>/dev/null)`
			`if [ $? -eq 0 ]; then`
			`exec $cmd "$script" "$@"`
fix `configure`: allow both `--enable-debug` and `--disable-debuginfo` in one invocation. 2015-07-20 08:07:53 +00:00			`fi`
			`}`

rustbuild: Rewrite the configure script in Python This commit rewrites our ancient `./configure` script from shell into Python. The impetus for this change is to remove `config.mk` which is just a vestige of the old makefile build system at this point. Instead all configuration is now solely done through `config.toml`. The python script allows us to more flexibly program (aka we can use loops easily) and create a `config.toml` which is based off `config.toml.example`. This way we can preserve comments and munge various values as we see fit. It is intended that the configure script here is a drop-in replacement for the previous configure script, no functional change is intended. Also note that the rationale for this is also because our build system requires Python, so having a python script a bit earlier shouldn't cause too many problems. Closes #40730 2017-08-26 22:01:48 +00:00			`try python2.7 "$@"`
			`try python27 "$@"`
			`try python2 "$@"`
			`exec python $script "$@"`