Update --ext=rust
to support compiling the native extension from source
#7610
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.
What was the end-user or developer problem that led to this PR?
I needed to apply some tiny changes to the skeleton generated by the
--ext=rust
option to compile my native extension from source.What is your fix for the problem, implemented in this PR?
When gem consumers install a gem with a native extension and their platform is not included the pre-compiled bundles, they need to compile it locally and rely on the
extconf.rb
file.Referencing the
extconf.rb
file in the gemspec is required to make that work. We also need to includerb_sys
as a dependency because the Rustextconf.rb
depends on it.Here's a demo of this change in action :)
Screen.Recording.2024-04-25.at.21.22.36.mov