Bundler platforms for Windows are messed up #589
Comments
Thank you for the bug report, and we will try to fix the issues you mention before the 1.0 final. In cas you need it later, the Bundler mailing list is at http://groups.google.com/group/ruby-bundler. |
So can we add a :mingw or make :mswin cover mingw? I would think ruby installer is the main way that people are using this. |
@gaffo, do mswin gems work with mingw? or are they incompatible? |
indirect are you on irc? gtalk? google talk? if so we can cover it there more easily. The long and short of it is that to get rubygems you either have to have a working compiler on windows (which isn't that common unless you are under cygwin) or you use the RubyInstaller which has rubygems installed for you. At least this is my experience. I'm not really sure if there is any difference between the 2 platforms. If they're not compatible then adding a mingw "platform" would be the other valid fix. But as things stand I can't use cucumber / rspec on windows and deploy to linux. I think @luislavena would be a very good one to get in on the converstation as well. |
It looks like cucumber at least is treating mswin and mingw as the same platform as luislavena said above. I think you are both online at the moment actually, as I've been talking to you both on here. Meet me in freenode #carlhuda if you get this. |
After talking with gaffo a bit, I've started trying to make MINGW a valid platform: http://github.com/carlhuda/bundler/tree/mingw Last I heard, gaffo made it to this error: http://gist.github.com/571211 I'm going to try to set up a Windows VM so that I can test this on my own machine. Input on how to reproduce the ruby setup you guys have would be highly appreciated, since I have no idea how ruby development on Windows works. :) |
Get windows installed. Run the ruby installer for 1.8.7. Install bundler, and start trying to break it :P. a good thing to do is a simple cuke / rspec setup, which will require the win32console. |
Hello indirect and thank you gaffo for jumping in. A basic environment will be get a Ruby version form RubyInstaller: http://rubyinstaller.org/downloads (recommend 1.8.7 for starting) and grab the Development Kit (which will provide a GCC toolset to install gems that require compilation. Later you can add other versions of Ruby and use Pik: http://github.com/vertiginous/pik to manage multiple installed versions. As for console, I recommend Console2: http://sourceforge.net/projects/console/files_beta/console-devel/2.00/ |
Hello,
Tried to reach wycats and carllerche on this in the past, and since there is no mailing list, decide to open "a bug".
The case is covered here:
http://gist.github.com/536191
Basically:
All the above cases render RubyInstaller useless. First, RubyInstaller is MinGW based, meaning that 'mswin' will not fit the bill.
Users indicating 'mswin' will force the installation of x86-mswin32 gems, when the platform is x86-mingw32, so if the user already had sqlite3-ruby-1.3.1-x86-mingw32.gem installed, it will attempt to install the mswin32 platform gem instead.
Users indicating 'ming' will get an error:
I commented in the past this to Yehuda that if platform :windows is proposed, the correct usage of both x86-mswin32 and x86-mingw32 should be considered.
I believe the current state and the documentation shown so far will lead to errors for these users and complains to RubyInstaller which, IMHO, are not the root of it.
Thank you.
The text was updated successfully, but these errors were encountered: