- Use `python2` executable if it exists, to avoid breakage on systems (such as Arch Linux) where `python` is Python 3. - Quote all references to `$0`, for safety when located in a directory containing spaces in its name. - Use the `exec` shell command to avoid leaving the shell wrapper in the process table when invoking the actual build tool. - Use `"$@"` rather than `$*` to pass arguments through directly rather than concatenating to a string, and then string-splitting and glob-expanding its contents. - Use `$BASH_SOURCE` in preference to `$0` (which is only guaranteed to be process name, *not* source path). Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Charles Duffy <chaduffy@cisco.com> Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@19694 6f19259b-4bc3-4df7-8a09-765794883524
15 lines
512 B
Bash
Executable File
15 lines
512 B
Bash
Executable File
#!/usr/bin/env bash
|
|
#python `dirname $0`/RunToolFromSource.py `basename $0` $*
|
|
|
|
# If a python2 command is available, use it in preference to python
|
|
if command -v python2 >/dev/null 2>&1; then
|
|
python_exe=python2
|
|
fi
|
|
|
|
full_cmd=${BASH_SOURCE:-$0} # see http://mywiki.wooledge.org/BashFAQ/028 for a discussion of why $0 is not a good choice here
|
|
dir=$(dirname "$full_cmd")
|
|
cmd=${full_cmd##*/}
|
|
|
|
export PYTHONPATH="$dir/../../Source/Python"
|
|
exec "${python_exe:-python}" "$dir/../../Source/Python/$cmd/$cmd.py" "$@"
|