preliminary support for clang64 #471
Merged
Conversation
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
support for clang64 dev environment installation and enablement. ridk install now accepts mingwarch, e.g `ridk install clang64 3`. after that, we can do with `ridk enable clang64`. this makes it easier for us to try developing ruby on clang64.
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.
This is not intended to implement a clang64 version of rubyinstaller, but rather to set up a clang64 development environment.
ridk installnow accepts mingwarch, e.gridk install clang64 3.after that, we can play with
ridk enable clang64.this makes it easier for us to try developing ruby on clang64.