You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build bundled-gem C extensions before configuring exts
`template/configure-ext.mk.tmpl` discovers bundled-gem C extensions
via `Dir.glob(".bundle/gems/**/extconf.rb", base: srcdir)` when
`ext/configure-ext.mk` is regenerated. Without an explicit dep,
`extract-gems` is not guaranteed to run first, so on a clean tree
the glob can return empty and bundled-gem extensions never make it
into `exts.mk`.
Add `extract-gems` as a prereq of `ext/configure-ext.mk`, gated on
`HAVE_BASERUBY` so the cross-compile path is unaffected. Once the
bundled-gem ext rules are in `exts.mk`, the existing per-extension
Makefile chain (`all: install` -> `install-so install-rb`) produces
the `.so`, the `gem.build_complete` marker, and the gemspec copy in
`.bundle/specifications/`.
Also tidy up the CI setup pipeline: extract `setup/baseruby` and
`setup/ubuntu` composite actions and use them from the cross-compile
and wasm workflows.
0 commit comments