Fix -o flag separator type#376
Merged
luser merged 1 commit intomozilla:masterfrom Mar 7, 2019
Jake-Shadle:out_fix
Merged
Conversation
Contributor
|
Gosh, compiler options are weird, aren't they? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When I tried to enable sccache for native compilation in addition to rust I ran into errors (the same kind as #189), I found that
ringwas causing sccache to fail because it's a bit more involved in the use ofccand when specifying the output object file is just directly concatenating the flag and the arg, so the command ends up beingJust changing the type of separator to support both
-ofileor-o fileallowed sccache to compileringsuccessfully.Resolves: #189