[Rubyinstaller-devel] Moving Ruby 1.9.1 forward on Windows
rogerdpack at gmail.com
Fri Apr 3 17:11:40 EDT 2009
Another thought would be to allow developers to develop in VS 2008.
Just instruct them that "when you want to distribute your code, you
may want to compile it using the mingw stack for highest
compatibility" or what not.
Also a recent note from Visual C++ express edition was "On March 31st
the Microsoft Visual Studio 2005 Express Edition products will be
discontinued and removed from www.microsoft.com/express" so I guess
Microsoft really does discontinue things :)
On Sat, Mar 28, 2009 at 3:47 PM, Roger Pack <rogerdpack at gmail.com> wrote:
> So if my theory is correct [I don't have all the information, but
> here's my guess]
> 1) if you are "careful" then you code, even though it was compiled
> against a different version of msvcrt.dll, will run in *any* windows
> ruby environment.
> I assume being careful means that you avoid the use off errno [and
> calling anything that uses errno]. Does anyone know which versions
> actually differ in errno numbering?
> If that's the case then we should be able to release the mingw version
> and then windows extension developers use VC 2008 and then package up
> their stuff "and name it mingw" [similar to currently doing a gem
> install --platform=mswin32].
> Am I off base?
> 2009/3/16 William Green <will at hotgazpacho.org>:
>> VC6 runtime may be on "all Windows", or available for download from
>> Microsoft, but the VC6 development tools (specifically, the compiler and
>> linker) are not available any longer, and I highly doubt they would even run
>> on Vista. So, unless you already have a copy of the VC6 dev tools, you
>> cannot obtain one now.
>> This, I believe, is the reason for the MingW32 build in the first place; all
>> the build tools are available, and not controlled by Microsoft.
>> Luis, am I totally off-base here, am I missing something?
>> On Mon, Mar 16, 2009 at 11:44 AM, Michal Suchanek <hramrach at centrum.cz>
>>> 2009/3/16 William Green <will at hotgazpacho.org>:
>>> > MSVC6 is no longer available from Microsoft (I've even checked my
>>> > Enterprisey MSDN Account... it is simply not available). This severely
>>> > limits the number of people who can build Ruby on Windows, if the
>>> > dependency
>>> > is kept. I'm pretty sure this is why Luis embarked on the mingw32 build
>>> > in
>>> > the first place.
>>> > If we MUST be dependent on an MS-provided C library, why not make it one
>>> > of
>>> > the ones that they distribute freely (with an IDE): 2005 or 2008.
>>> > Question is, though, is this truly a dependency?
>>> Yes, it is. These are not installed in Windows (nor Wine) by default
>>> and you have to distribute them with Ruby for it to work. And they are
>>> some special beast so just downloading the dll and dropping it into
>>> the ruby directory is not enough if you forget to bundle it.
>>> On the other hand, the VC6 runtime is in all Windows so it is not a
>>> Rubyinstaller-devel mailing list
>>> Rubyinstaller-devel at rubyforge.org
>> Will Green
>> Rubyinstaller-devel mailing list
>> Rubyinstaller-devel at rubyforge.org
More information about the Rubyinstaller-devel