Manually fix warnings in google code instead of waiting for google #14
Conversation
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
… figure their shit out
logankaser
changed the title
|
what is that other binary you replaced it with? an older version? Can you not get the older version from brew? |
Brew only has native librairies i.e for x86_64, I have to custom compile this for WASM, it's never been from brew (except for the server). Those two 7z files are the WASM version I compiled. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
instead of waiting for google to figure their shit out..
It's been three months and google can't be bothered to fix the used variable warnings they have.
So I did it.
Two
(void)varlater it compiles with no warnings. Yup all those warnings were from two places.