I started getting the following message when requiring win32ole:
warning: win32ole was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.
You can add win32ole to your Gemfile or gemspec to silence this warning.
However, when I added it explicitly to the gemspec, it starts crashing on bundle install, as it's trying to compile the C extensions.
The problem seems to be that win32ole does not ship with a java platform build, and for that, a separate jruby-win32ole is registered as a gem in rubygems. I'm assuming that this mostly works when using the standard packaged version, but becomes a problem when explicitly declaring the dep (a la jruby-openssl, which suffers from the same problem).
I wonder whether this is something that can be fixed for ruby 4.0.0 by integrating this repo in the main one. I'm guessing that should be lower friction than what's preventing the jruby-openssl code from being deployed to the core repo as well?
I started getting the following message when requiring
win32ole:However, when I added it explicitly to the gemspec, it starts crashing on
bundle install, as it's trying to compile the C extensions.The problem seems to be that
win32oledoes not ship with a java platform build, and for that, a separatejruby-win32oleis registered as a gem in rubygems. I'm assuming that this mostly works when using the standard packaged version, but becomes a problem when explicitly declaring the dep (a lajruby-openssl, which suffers from the same problem).I wonder whether this is something that can be fixed for ruby 4.0.0 by integrating this repo in the main one. I'm guessing that should be lower friction than what's preventing the
jruby-opensslcode from being deployed to the core repo as well?