-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support default & bundled extension gems #2644
Comments
Do JRuby have an approach to this problem? Do they all include Java code? |
Yes basically JRuby's approach so far is to mostly upstream their JRuby-specific extension Java code into those default gems' repositories (and publish a java platform gem). |
Here is a list of default gems with extensions in 3.1:
And for the raw list:
We should prioritize adding truffleruby in the CI of those to make sure they work and keep working on truffleruby. |
This an issue to track all default gems with an extension, which might need specific support for TruffleRuby.
For some, we might just reuse the C extension and add TruffleRuby in the CI of those gems.
These default extension gems are problematic when they included in a Gemfile.lock, https://bugs.ruby-lang.org/issues/18567#note-30 has more details.
Related JRuby issue: jruby/jruby#6682
For some extensions gems, we have a different implementation, typically pure-Ruby.
For some extensions gems we use them as-is (just need to add truffleruby in CI).
ruby/digest.h
Pure-Ruby gems (good to add truffleruby in CI):
The text was updated successfully, but these errors were encountered: