I don't know if this is old news or not, but I was just playing around and I
wanted to see if I could get Watir to install with 1.9.2p0 which is the new
one-click installer that was released back in August.  If you run 'gem
install watir' this will work fine without complaining.  However, whenever
you do a Watir::IE.new or Watir::Browser.new, you get a popup saying: "The
program can't start because msvcrt-ruby18.dll is missing from your
computer".  This was followed by this stacktrace:

C:\Users\Alan\DevKit>irb --noreadline
irb(main):001:0> require 'watir'
=> true
irb(main):002:0> br = Watir::Browser.new
LoadError: 126: The specified module could not be found.   -
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/win32-api-1.4.6-x8
6-mingw32/lib/win32/api.so
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.6.7/lib/watir/browser.rb:89:in
`eval'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/windows-api-0.4.0/lib/windows/api.rb:1:in
`<top (required)>'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/windows-pr-1.1.2/lib/windows/error.rb:12:in
`<top (required)>'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/win32-process-0.6.4/lib/win32/process.rb:1:in
`<top (required)>'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.6.7/lib/watir/ie-process.rb:1:in
`<top (required)>'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from <internal:lib/rubygems/custom_require>:29:in `require'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.6.7/lib/watir/ie.rb:5:in
`<top (required)>'
        from (eval):1:in `klass'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.6.7/lib/watir/browser.rb:89:in
`eval'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.6.7/lib/watir/browser.rb:89:in
`klass'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.6.7/lib/watir/browser.rb:79:in
`set_options'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.6.7/lib/watir/browser.rb:142:in
`set_sub_options'
        from
C:/ruby/Ruby192/lib/ruby/gems/1.9.1/gems/commonwatir-1.6.7/lib/watir/browser.rb:64:in
`new'
        from (irb):2
        from C:/ruby/Ruby192/bin/irb:12:in `<main>'irb(main):003:0> exit


After looking around I found this thread:
http://groups.google.com/group/rubyinstaller/browse_thread/thread/d9c226735a54679f
that
talks about how to fix this.  Basically you have to get the DevKit (4.5.0)
from rubyinstaller.org (directions here:
https://github.com/oneclick/rubyinstaller/wiki/Development-Kit) so that you
can run the following (after having installed Ruby 1.9.2, the DevKit and
Watir 1.6.7):

C:\Users\Alan\DevKit>gem uninstall win32-api

Select gem to uninstall:
 1. win32-api-1.4.6
 2. win32-api-1.4.6-x86-mingw32
 3. All versions
> 3
Successfully uninstalled win32-api-1.4.6
Successfully uninstalled win32-api-1.4.6-x86-mingw32

C:\Users\Alan\DevKit>gem install win32-api --platform=ruby
Temporarily enhancing PATH to include DevKit...
Building native extensions.  This could take a while...
Successfully installed win32-api-1.4.6
1 gem installed
Installing ri documentation for win32-api-1.4.6...
Installing RDoc documentation for win32-api-1.4.6...

C:\Users\Alan\DevKit>gem list win32-api --local

*** LOCAL GEMS ***

win32-api (1.4.6)

C:\Users\Alan\DevKit>irb --noreadline
irb(main):001:0> require 'watir'
=> true
irb(main):002:0> br = Watir::Browser.new
=> #<Watir::IE:0x289bfa60 url="about:blank" title="">
irb(main):003:0> br.goto('google.com')
=> 0.468027
irb(main):004:0> exit


Success!  Anyway, I thought it was cool.  Hopefully this will save someone
some trouble.  Obviously, this isn't quite ready for prime-time yet, but at
least we can get a look at Watir with 1.9.2.

I haven't tested any farther than opening the browser.

Alan
_______________________________________________
Wtr-development mailing list
Wtr-development@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-development

Reply via email to