Skip to content

Supporting for JRuby? #396

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

Closed
ryudoawaru opened this issue Aug 18, 2024 · 2 comments
Closed

Supporting for JRuby? #396

ryudoawaru opened this issue Aug 18, 2024 · 2 comments

Comments

@ryudoawaru
Copy link

It seems this gem does not support JRuby now because Gem::Platform.local.cpu&os only respond java & universal.

I would like to commit a PR to support JRuby by using RbConfig::CONFIG instead of Gem::Platform and I want to make sure if this project would like to add support of JRuby?

Thanks,

@flavorjones
Copy link
Member

I'm open to adding support to JRuby, but I am hesitant to add much complexity for that support. Let's discuss what approach you have in mind!

I see that I can find the architecture, at least on some platforms, in RbConfig::CONFIG["target_cpu"] when running JRuby. But what will you do with that information? This project currently ships separate gem files for each architecture, is your intention to ship all the executables in the JRuby gem package (and then choose the executable at runtime or install time)?

Would it be simpler to improve the documentation on how to install the appropriate binary outside of Rubygems and then leverage the existing docs at https://github.com/rails/tailwindcss-rails?tab=readme-ov-file#using-a-local-installation-of-tailwindcss ?

@flavorjones
Copy link
Member

Closing since this gem no longer packages the tailwindcss binaries (that's done by https://github.com/flavorjones/tailwindcss-ruby). I'm happy to discuss further if you want to open a discussion or issue on that repository! But my questions from above are still valid, I think.

@flavorjones flavorjones closed this as not planned Won't fix, can't repro, duplicate, stale Jan 27, 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

No branches or pull requests

2 participants