Feature: Make non-zero exit code available when compiler compile fails#7
Conversation
|
There's some failed checks. As discussed in #2 (comment), if we decide to no longer support wrappers |
I'd actually be open adding support for exit codes for when compiler wrapper scripts are invoked, and more so than supporting #2. Should we decide to continue support for invoking compiler wrappers, I'll see how I can contribute to make this feature robust if possible. |
2143301 to
e6fb4e0
Compare
…ries in Compile-SourceScript()
e6fb4e0 to
e1fe437
Compare
…cemod compiler or amxmodx compiler wrapper is used
1c50592 to
3a06f36
Compare
…xmodx compiler or compiler wrapper is used
…Windows sourcemod compiler or compiler wrapper is used
…mod compiler or amxmodx compiler wrapper is used
joeltimothyoh
left a comment
There was a problem hiding this comment.
lgtm. Please review @leojonathanoh
|
Pinging @leojonathanoh |
…nd preparation of compilation environment
8fcff17 to
b77e9cf
Compare
… errors in: compilation via compiler binary and compilation via compiler wrapper
35d5c97 to
5f4dceb
Compare
…etect errors in: compilation via compiler binary and compilation via compiler wrapper
086fd6e to
d9751aa
Compare
…, compile, and compilation cleanup stages to ensure cleanup occurs
|
Merging. |
|
Should we do a merge commit or squash merge? @leojonathanoh |
|
either will do |
|
In terms of OSS workflow and git history? @leojonathanoh |
|
Pinging @leojonathanoh |
|
i prefer merge commits since it’s more traceable |
|
Ok but we’ve already begun using squash commits in some other projects. Also release notes would be less readable or understandable. @leojonathanoh |
|
Merging via a merge commit as discussed with @leojonathanoh. |
Fixes #6