From: ptkwt@...2.teleport.com (Phil Tomson)
Date: 2001-02-01T05:40:02+09:00
Subject: [ruby-talk:10190] Re: system command on Windows(Arrgghhh!)

In article <slrn97gigh.6hl.andy@workbench.toolshed.com>,
Andrew Hunt <Andy@Toolshed.Com> wrote:
>On 28 Jan 2001 23:08:10 -0800, Phil Tomson <ptkwt@user2.teleport.com> wrote:
>> In article <9504t2$4lp$1@b5nntp2.channeli.net>,
>> 酵費七\(Park, Hee-Sob\) <phasis@channeli.net> wrote:
>> >
>> >"Phil Tomson" <ptkwt@user2.teleport.com> wrote in message
>> 
>> Hmmm... So that's what's going on.  So the self-installing Windows version
>> of Ruby is build on cygwin and that leads to these sorts of problems.
>> Could someone make a Ruby Binary build with Visual C++ available?
>
>I am currently wrapping up eban's cygwin distribution for the
>Windows Installer as the cygwin version seems to have more
>features and such, but I'd be happy to wrap up one of the
>other distributions instead if they were "better".
>
>The real problem is that there is no single "official" port of
>Ruby to Windows, there are instead several flavors, each
>with its own pros and cons.
>

So, I imagine that there were several ports of Perl for windows prior to
ActiveState's port and that they probably had similar problems as Ruby on
Windows is now having. (I never used Perl on Windows prior to ActiveState
perl, so I don't know for sure) 

What exactly did ActiveState do differently to port Perl to Windows and
can the same be done for Ruby?

Why would compiling Ruby with Visual C++ cause some features to be missing
(like popen)?

Phil