-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Universal gems do not match x64-mingw32 platform #3066
Comments
I think universal gems are a new thing that isn’t explicitly supported by Bundler yet. If you understand how they are supposed to be supported, a patch would be fantastic. If not, we’ll try to get this working soon. Thanks for letting us know! On Jun 13, 2014, at 11:07 PM, Josh Cooper notifications@github.com wrote:
|
This is fixed in 1.9.3 |
I have a Gemfile:
Currently,
windows-api
is at version0.4.2
. It has a dependency onwin32-api
.In ruby 1.9.3p374, bundler successfully resolves the most recent version of the gem, which happens to be
win32-api-1.5.1-universal-mingw32
, containing precompiled binaries for both x86 and x64.However, on ruby 2.0.0p481 x64, the universal gem does not match, and bundler falls back to
win32-api-1.4.8
, which is aruby
version that requires the DevKit to be installed to compile the native extension.However,
gem install windows-api
on ruby 2.0.0 x64 correctly pulls in thewin32-api-1.5.1-universal-mingw32
gem as expected:There seems to be an issue with how bundler compares the current
x64-mingw32
platform against possible matches. I would expect it to prefer an exact match, e.g.x64-mingw32
, but fall back touniversal-mingw32
before trying earlier versions.The text was updated successfully, but these errors were encountered: