Ok, it seemed that pik installed only legacy DevKit. I just created a fresh VM and installed DevKit like you guys did and succeeded to build win32-api. So, ruby does not need to be installed from the ruby installer, but works also with pik install, just FYI.
Jarmo On Fri, Dec 3, 2010 at 5:58 AM, marekj <marekj....@gmail.com> wrote: > On Thu, Dec 2, 2010 at 2:15 PM, Alan Baird <aba...@bairdsnet.net> wrote: > > Actually, I think what I did was: > > 1) Install Ruby 1.9.2p0 from the one-click installer (not using pik) > > 2) Add that installation using: pik add c:\ruby\Ruby192\bin > > 3) Installed Watir > > 4) Installed the dev kit using; 'ruby dk.b init', then 'ruby dk.rb > install > > OK, I am with Alan on this one > > cd <DEVKIT_INSTALL_DIR> > ruby dk.rb init > ruby dk.rb review > ruby dk.rb install > > should set rubygems pre_install hook to ensure that --platform=ruby uses > devkit > > > > 5) ran what you saw in the first email > > Dunno if that will make a difference. > > Alan > > _______________________________________________ > > 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
