emsdk_env.sh

# This script is sourced by the user and uses
# their shell. Try not to use bashisms.

# Do not execute this script without sourcing,
# because it won't have any effect then.
# That is, always run this script with
#
#     . ./emsdk_env.sh
# or
#     source ./emsdk_env.sh
#
# instead of just plainly running with
#
#     ./emsdk_env.sh
#
# which won't have any effect.
SRC="$BASH_SOURCE"
if [ "$SRC" = "" ]; then
  SRC="$0"
fi
CURDIR="$(pwd)"
cd "$(dirname "$SRC")"
unset SRC

tmpfile=`mktemp` || exit 1
./emsdk construct_env "$@" $tmpfile
. $tmpfile
rm -f $tmpfile

cd "$CURDIR"
Improve cross-shell compatibility 2014-11-18 00:42:02 +00:00			`# This script is sourced by the user and uses`
			`# their shell. Try not to use bashisms.`

Add a comment to emsdk_env.sh to remind that it's supposed to be sourced. 2014-12-30 18:55:49 +02:00			`# Do not execute this script without sourcing,`
			`# because it won't have any effect then.`
			`# That is, always run this script with`
			`#`
			`# . ./emsdk_env.sh`
			`# or`
			`# source ./emsdk_env.sh`
			`#`
			`# instead of just plainly running with`
			`#`
			`# ./emsdk_env.sh`
			`#`
			`# which won't have any effect.`
Improve cross-shell compatibility 2014-11-18 00:42:02 +00:00			`SRC="$BASH_SOURCE"`
			`if [ "$SRC" = "" ]; then`
Use $0 to get execution path $_ is "The last argument of the previous command." (cf. man zshparam) on zsh, so SRC will be "]". 2015-04-15 20:42:18 +09:00			`SRC="$0"`
Improve cross-shell compatibility 2014-11-18 00:42:02 +00:00			`fi`
Fix path quoting bug introduced in #220 (#227) It seems that some variables were mistakenly left unquoted, leading to paths containing spaces being treated incorrectly. For example, the directory `/home/person/foo bar/test/` would cause `CURDIR=$(pwd)` to be expanded to `CURDIR=/home/person/foo bar/test/`. This means that the shell would attempt to run the command `bar/test/` with the environment variable `CURDIR` set to `/home/person/foo`. This is due to [word splitting](https://www.gnu.org/software/bash/manual/html_node/Word-Splitting.html). (TL;DR the result of shell expansions should probably be quoted 99% of the time) 2019-03-06 11:35:35 -05:00			`CURDIR="$(pwd)"`
			`cd "$(dirname "$SRC")"`
Improve cross-shell compatibility 2014-11-18 00:42:02 +00:00			`unset SRC`
Migrate OSX shell activation to work the same way as on Windows: source ./emsdk_env.sh instead of emsdk_add_path. 2014-07-03 18:50:00 +03:00
Avoid file creation/deletion races in emsdk_env.sh by using a temporary file(#307) Fixes https://github.com/emscripten-core/emscripten/issues/9090. 2019-07-26 19:50:10 -04:00			tmpfile=`mktemp` \|\| exit 1
			`./emsdk construct_env "$@" $tmpfile`
			`. $tmpfile`
			`rm -f $tmpfile`
Improve cross-shell compatibility 2014-11-18 00:42:02 +00:00
Fix path quoting bug introduced in #220 (#227) It seems that some variables were mistakenly left unquoted, leading to paths containing spaces being treated incorrectly. For example, the directory `/home/person/foo bar/test/` would cause `CURDIR=$(pwd)` to be expanded to `CURDIR=/home/person/foo bar/test/`. This means that the shell would attempt to run the command `bar/test/` with the environment variable `CURDIR` set to `/home/person/foo`. This is due to [word splitting](https://www.gnu.org/software/bash/manual/html_node/Word-Splitting.html). (TL;DR the result of shell expansions should probably be quoted 99% of the time) 2019-03-06 11:35:35 -05:00			`cd "$CURDIR"`