On Jan 12, 2008 4:23 PM, Wes G. [email protected] wrote:
Based on my testing, it appears to me there is something that Mongrel is
loading that is requiring MSVCR80.dll, since 1.0. Isn’t that correct?
No, all the version of mongrel are build with VC6, so the http11
extension is linked to MSVCRT.dll, and not MSVCR80.dll
can you try this on a IRB console?
irb(main):002:0> require ‘rubygems’
=> true
irb(main):003:0> require ‘mongrel’
=> true
irb(main):004:0> Mongrel::Const::MONGREL_VERSION
=> “1.1.2”
If you don’t get the msgbox in that process is because mongrel isn’t
responsible for that. If you get, I’ll suggest you remove the mongrel
gem and clean install it again.
I know. Honestly, I’ve enjoyed the “underdog” role of being “the only
or one of few Windows guys in the room” at Ruby/Rails gathering to some
degree. And when I get the sense that there is Mac elitism at work, it
really bugs me. But, if I’m going to use Rails as a major tool in my
work, it behooves me to make it as easy as possible for myself to
develop. Back when I was doing mostly Java work, it didn’t really
matter that I was on Windows.
Since I started with Rails (back in 0.13) I didn’t have too many
troubles with it. Ruby, by itself, didn’t showed my troubles neither.
But some of the “popular libraries” have them, mostly because some
developers ignores other platforms (part of their elitism or
ignorance).
I use Rails on a daily basis to deploy to linux servers, all without
glitches (trust me: noone).
ssh to some server? no problem. have all your ssh keys? no problem
(pageant, putty ssh agent).
Anyway, I found no problems using Rails on Windows, except those
plugins from some developers that didn’t care about good/fair usage of
resources or the true nature of ruby a being cross-platform language.
–
Luis L.
Multimedia systems
A common mistake that people make when trying to design
something completely foolproof is to underestimate
the ingenuity of complete fools.
Douglas Adams
