From: daz <dooby@...10.karoo.co.uk>
Date: 2004-06-19T05:28:20+09:00
Subject: Re: ruby one-click installer issue with extensions


Curt Hibbs wrote:
>
> Since the Ruby Installer for Windows is compiled natively (with VC++ 7.1),
> and your extension is compiled with mingw32, I would expect problems, and
> perhaps that is the source of the segfaults [...].
>
> I'm going to cross post this to the ruby-talk ML, and the ruby-installer-dev
> ML to get some other opinions on this.
>

Hi Curt,

*Just* an opinion ...

I wonder if it's _generally_ possible for users of a one-click installer
to use the Ruby process to add C extensions locally?

Part of your build creates config.h, config.status & rbconfig.rb which
reflect your environment, as you know.
Data such as compiler options are taken from here as input to mkmf.rb
but bear little, or no relation to the user's environment.

To be able to install C extensions easily, my assumption was that a
self-built Ruby would be a prerequisite unless a user was prepared to do
some serious reworking of the generated makefiles and, maybe, others.


daz