Skip to content

feat: add native extension support#222

Open
YOU54F wants to merge 2 commits intomasterfrom
feat/native_exts
Open

feat: add native extension support#222
YOU54F wants to merge 2 commits intomasterfrom
feat/native_exts

Conversation

@YOU54F
Copy link
Member

@YOU54F YOU54F commented Jan 9, 2026

also updates ruby to 3.3.10

@YOU54F YOU54F force-pushed the feat/native_exts branch 3 times, most recently from 31d9f57 to 01899fa Compare January 9, 2026 16:06
@YOU54F YOU54F changed the title feat: add native extension support, update rust tools, rename osx to … feat: add native extension support Jan 9, 2026
@YOU54F YOU54F marked this pull request as ready for review January 9, 2026 16:21
@YOU54F YOU54F mentioned this pull request Jan 9, 2026
@mefellows
Copy link
Member

So if I understand correctly, you now download and bundle OS-arch specific gems into the distribution? What was the behaviour prior to this change? It just used non-native versions of the packages or were there issues?

@YOU54F
Copy link
Member Author

YOU54F commented Jan 12, 2026

So if I understand correctly, you now download and bundle OS-arch specific gems into the distribution? What was the behaviour prior to this change? It just used non-native versions of the packages or were there issues?

yes, we have had to pin to versions of native gems that are packaged with ruby, updating the versions only when we update ruby.

the main issue was due to windows traveling ruby not supporting native extensions so in order to build the packages for all the platforms, we excluded native gens entirely

this change gives us the latest versions of each native gem we support, which aids us if ruby ever removes from those from the standard gem set, which they are doing release on release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants