Skip to content

Comments

Make it possible to override RUBY_TARGET#512

Merged
ianks merged 2 commits intooxidize-rb:mainfrom
stanhu:sh-fix-ruby-target-try2
Jan 30, 2025
Merged

Make it possible to override RUBY_TARGET#512
ianks merged 2 commits intooxidize-rb:mainfrom
stanhu:sh-fix-ruby-target-try2

Conversation

@stanhu
Copy link
Contributor

@stanhu stanhu commented Jan 30, 2025

This reverts #511 because the CI test expected that rb-sys-dock --platform x86_64-linux --directory . --build produces a gem with a suffix of -x86_64-linux.gem.

This change drops the hard-coded RUBY_TARGET from the bash script so the value can be derived from the ENV setting. With this change, this is now possible:

  1. rb-sys-dock --platform x86_64-linux --directory . --build produces a gem with a filename -x86_64-linux-gnu.gem.
  2. rb-sys-dock --platform x86_64-linux-gnu --directory . --build produces a gem with a filename -x86_64-linux-gnu.gem.

Previously if you attempt to run `rb-sys-dock --platform x86_64-linux-gnu`
the `RUBY_TARGET` was hard-coded to `x86_64-linux`. Now this can
be overriden by the `rb-sys-dock` so that the `--platform` argument
can work with `x86_64-linux` or `x86_64-linux-gnu`.
@ianks ianks merged commit 7b03755 into oxidize-rb:main Jan 30, 2025
56 checks passed
@stanhu
Copy link
Contributor Author

stanhu commented Jan 30, 2025

I seem to be making things worse here: https://github.com/oxidize-rb/rb-sys/actions/runs/13059416829/job/36438458768

I'm not sure why RUBY_TARGET is duplicated in so many places. At this point it almost seems easier to create a new Dockerfile for the GNU builds and drop this alias business.

stanhu added a commit to stanhu/rb-sys that referenced this pull request Jan 30, 2025
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