* Use sh alternatives and fix change directory in building shell scripts The usage of the cd command in the shell scripts under building/ can conflict at some point during the procedure. As far as I'm aware, it's supposed to cd to the parent directory, but it does so strangely. On some occasions, this may cause the directory to switch to /tmp on Linux instead. This commit resolves that by instead using the typical .. syntax, which is a shorthand for the parent directory of the process. Additionally, proper shebangs have been added that instead use "/usr/bin/env sh", which returns the path to a suitable sh alternative: that is, the closest program that can be found using 'sh' in the name. This is one of the most recommended shebangs for a shell script, due to 'env' typically being in the exact same position. * Update cd in building shell scripts to use script relative path properly The two prior versions would use the working directory's own parent directory, not the script's. This commit simply makes it so that changing the directory in the script uses its directory's parent instead. * dont mind me --------- Co-authored-by: ⍚~Nex <87421482+NexIsDumb@users.noreply.github.com>
3 lines
100 B
Bash
Executable File
3 lines
100 B
Bash
Executable File
#!/usr/bin/env sh
|
|
cd "$(dirname "$0")/.."
|
|
haxe -cp commandline -D analyzer-optimize --run Main setup |