Repository navigation
Conversation
The custom ext:build task can cause misterious errors when running "rake compile test". * Rakefile (test): Remove ext:build from and add compile to the test task. (ext): Remove namespace.
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
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.
Hello, this is various minor setup improvements, including:
compiletask ...(a)require_relativeand unshifting to$LOAD_PATH)stdbool.hheader for boolean type and valuesurigem by explicitly requiring in advanceAdditional note about (a)
The custom
ext:buildtask seems to cause a race issue betweenclobberandcompilein some case like invokingrake compile test:Thank you!