Hey Jeff et al, Thanks for sending the mail. I immediately saw what I glossed over when we were chatting, it is in fact the problem I suspected with a gem that was compiled with Visual Studio 2005 - namely win32-api. For the past two releases - 1.3.0 and 1.4.0, there are 3 versions of the win32-api gem: win32-api-1.4.0-x86-mswin32-80.gem win32-api-1.4.0-x86-mswin32-60.gem win32-api-1.4.0.gem
Rubygems makes the best guess for your platform when installing gems, the gems above should rely on your ruby environment to pick the right one, the first is for systems that match the environment set in the gem metadata: x86-mswin32-80 - windows Ruby compiled with VS2005 (the msvc runtime version 8), the second one should match the normal Windows one click installer version of Ruby compiled with MSVC6, and the third would be installed on systems where you'd compile the shared libraries for the gem on your system. I didn't realize there are now multiple versions of the gem. There's been some development using VS2005 or minGW to compile 1.9.1 for the next One Click Installer to replace the over 10 year old, hard to find MSVC6 compiler to create the c extensions and libraries used by ruby and other gems. I'd assume this new gem 80 is for some of that work. I'm not quite sure why Rubygems is installing this particular version in some cases, if anyone is still having the issue or can reproduce it, let me know. You can force gems to install the right version, but I'm also curious to see why this is happening. gem install win32-api --platform x86-mswin32-60 Thanks, Charley Baker blog: http://charleybakersblog.blogspot.com/ Lead Developer, Watir, http://wtr.rubyforge.org QA Architect, Gap Inc Direct On Fri, Feb 20, 2009 at 7:27 PM, Jeff Fry <jeff....@gmail.com> wrote: > Al: Yeah, I was referencing that thread above. It pointed toward Visual > Studio, which I don't have. Charley theorized off list that one of the gems > on my system might have been compiled using Visual Studio. > Bret: Doh. Typo, but the first error ("msvcr80-ruby18.dll was not found") was > occuring when I did anything watir-related, including valid things like > running tests that used to work or doing > > irb(main):002:0> Watir::IE::VERSION > > That said, I just uninstalled and reinstalled ruby 1.8.5 > 1.8.6, and then > reinstalled watir...and all seems to be working for me now. > > Thanks! > Jeff > > On Fri, Feb 20, 2009 at 6:10 PM, Bret Pettichord <b...@pettichord.com>wrote: > >> >> Jeff Fry wrote: >> > >> > irb(main):003:0> Watir::IE::BROWSER >> > NameError: uninitialized constant Watir::IE::BROWSER >> > from (irb):3 >> This is correct, and what I get too. >> >> There is no such thing as Watir::IE:BROWSER. >> >> Bret >> >> >> >> >> > > > -- > Jeff Fry > > http://testingjeff.wordpress.com > http://associationforsoftwaretesting.org > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Watir General" group. To post to this group, send email to watir-general@googlegroups.com Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to watir-general-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/watir-general -~----------~----~----~----~------~----~------~--~---
