-
Notifications
You must be signed in to change notification settings - Fork 867
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* dev.sh: use dash instead of slash for msbuild Instead of switching between windows and non-windows to determine how to handle slashes for msbuild, use dashes instead of slashes to simplify the calling. * dev.sh: stop on errors Stop on errors, instead of continuing. This prevents us from failing to move through the directory space with `cd` / `pushd` / `popd` but still running commands. This is particularly dangerous when running commands like `rm`. * dev.sh: quote all filepaths Since directories may have a space in them, quote them to treat them as a single entity instead of wordsplitting on a space. Otherwise, if `FOO="a b c"` then `rm -rf $FOO` will remove files or folders named `a`, b`, and `c` instead of removing the single entity named `a b c`. * dev.sh: remove files carefully When expanding variables to pass to `rm`, make sure that the path variable is set and fail if it is not. This prevents an `rm` from accidentally expanding to `rm ""/*` when the variable is unset: ValveSoftware/steam-for-linux#3671 Using `${FOO:?}` syntax will fail when `FOO` is unset. * dev.sh: quote the `$` in `$LastExitCode` `$LastExitCode` is not a bash variable; to pass that string along to PowerShell, it needs to be quoted. * dev.sh: use $(cmd) syntax instead of backticks The $(cmd) execution syntax is preferred over the legacy backtick syntax. * dev.sh: quote variables * externals.sh: quote variables to cope with spaces Quote the variables for the directories so that we can properly work with directories with spaces in their names.
- Loading branch information
1 parent
4d4b1e6
commit d3575d5
Showing
2 changed files
with
40 additions
and
50 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters