I haven't seen that extra line as an output ever while using pik, but devkit
itself is installed also via pik by `pik install devkit` and it ought to be
know about my ruby and vice versa. I wonder if there's some easy way to make
sure... anyone knows?

Jarmo

On Thu, Dec 2, 2010 at 6:56 PM, marekj <marekj....@gmail.com> wrote:

> On Thu, Dec 2, 2010 at 7:26 AM, Jarmo <jarm...@gmail.com> wrote:
> > Nice job to make it work. I have had also some thoughts to try it out on
> > 1.9.2 but haven't got the time to do that. I was aware that there is no
> > prebuilt binary for win32 gems also.
> > marekj: in Windows there is pik to have multiple installations of Ruby :)
> > Check it out https://github.com/vertiginous/pik
> >
> > Just gave it a try and failed:
> > C:\Users\jarmo>gem install win32-api --no-rdoc --no-ri --platform=RUBY
> > Building native extensions.  This could take a while...
> > ERROR:  Error installing win32-api:
> >         ERROR: Failed to build gem native extension.
>
> at the time that you have 1.9.2 an active ruby and you have devkit
> installed somewhere I think you have to run some seutp to make ruby
> know here devkit is.
> It looks like the --platform=ruby switch here did not use devkit. I
> usually see this line
>
> Temporarily enhancing PATH to include DevKit...
>
> but your output didn't have it.
>
> > C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/bin/ruby.exe extconf.rb
> > checking for strncpy_s()... *** extconf.rb failed ***
> > Could not create Makefile due to some reason, probably lack of
> > necessary libraries and/or headers.  Check the mkmf.log file for more
> > details.  You may need configuration options.
> > Provided configuration options:
> >         --with-opt-dir
> >         --without-opt-dir
> >         --with-opt-include
> >         --without-opt-include=${opt-dir}/include
> >         --with-opt-lib
> >         --without-opt-lib=${opt-dir}/lib
> >         --with-make-prog
> >         --without-make-prog
> >         --srcdir=.
> >         --curdir
> >         --ruby=C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/bin/ruby
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:368:in
> > `try_do': The complier failed to generate an executable file. (Runtime
> > Error)
> > You have to install development tools first.
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:435:in
> > `try_link0'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:440:in
> > `try_link'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:552:in
> > `try_func'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:797:in
> > `block in have_func'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:693:in
> > `block in checking_for'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:280:in
> > `block (2 levels) in postpone'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:254:in
> > `open'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:280:in
> > `block in postpone'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:254:in
> > `open'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:276:in
> > `postpone'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:692:in
> > `checking_for'
> >         from
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:796:in
> > `have_func'
> >         from extconf.rb:9:in `<main>'
> >
> > Gem files will remain installed in
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/gems/1.9.1/gems/win32-api-1.4.6
> > for inspection.
> > Results logged to
> >
> C:/Users/jarmo/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/gems/1.9.1/gems/win32-api-1.4.6/ext/gem_make.out
> > C:\Users\jarmo>ruby -v
> > ruby 1.9.2dev (2010-05-31) [i386-mingw32]
> > I have devkit installed of course and it has built something for me
> before.
> > Jarmo
> >
> > On Thu, Dec 2, 2010 at 2:52 PM, marekj <marekj....@gmail.com> wrote:
> >>
> >> I've done this experiment too  on Win7 with Ruby 1.9.2 and DevKit 4.5
> >> I installed into c:/ruby192 and c:/rubydevkit450 respectively
> >> I also have c:/ruby186 for my regular ruby.
> >> So if I want to swtich  ruby env I have to adjust the PATH (either
> >> c:\ruby1xx\bin) and reboot. ( I use rvm for linux and it switches ruby
> >> env great)
> >>
> >> I ran my watirloo tests successfully on 1.9.2 . The only problem is
> >> that I get segfault when I run threaded tests when I drive multiple
> >> browsers.
> >>
> >>
> https://github.com/marekj/watirloo/blob/master/spec/browser_threads_spec.rb
> >> all others ran find (on IE8)
> >>
> >> Warning: before running tests I have to adjust load path since ruby
> >> 1.9.2 no longer puts current dir on load path
> >>
> >>
> http://stackoverflow.com/questions/2900370/why-does-ruby-1-9-2-remove-from-load-path-and-whats-the-alternative
> >> This ended up trivial, very easy change.
> >> here is an example of global replace
> >>
> >>
> https://github.com/jeremyevans/sequel/commit/36eabe31d10f0e9ee71ce1063852939807f446ea
> >>
> >> My change is like this
> >> -require File.dirname(__FILE__) + '/spec_helper'
> >> +require File.dirname(File.expand_path(__FILE__)) + '/spec_helper'
> >>
> >> One thing I did not try yet is modal dialogs and js popups tests.
> >> Not sure if autoit works.
> >>
> >>
> >> marekj
> >>
> >> http://rubytester.com
> >> _______________________________________________
> >> Wtr-development mailing list
> >> Wtr-development@rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/wtr-development
> >
> >
> > _______________________________________________
> > Wtr-development mailing list
> > Wtr-development@rubyforge.org
> > http://rubyforge.org/mailman/listinfo/wtr-development
> >
> _______________________________________________
> Wtr-development mailing list
> Wtr-development@rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-development
>
_______________________________________________
Wtr-development mailing list
Wtr-development@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-development

Reply via email to