From: "Gerardo Santana Gómez Garrido" Date: 2008-04-07T23:22:24+09:00 Subject: Re: gem build documentation for new gems? On 4/7/08, Phillip Gawlowski wrote: > | Fortunately it doesn't happen everywhere. OpenBSD for example, they do > | not add any feature if it is not documented. > > And we (all of us, I'm guilty of providing insufficient documentation > myself) need to strive to set the bar as high as possible. Indeed. I do my share also. > | > | Why not compile natively on Windows? > > Setting up a MinGW/MSYS environment is a bit of a hassle, especially if > you want GCC 4, since the MinGW32 folks lag behind on that. Have you tried the latest attempt from Luis Lavena? You can easily build msys, mingw32 and Ruby just typing 'rake'. http://blog.mmediasys.com/ I have successfully built a C extension with it. And it works. > However, I've asked myself that same question. Trouble would be to > define the Ruby environment for building extensions for things like > GTK+/GNOME2, which are available pre-compiled at the moment (storage of > header-files, how mkmf works, what needs to be handled, etc. In short, I > don't know the scope of this tangled mess just yet, and can't start > unraveling the threads). > > The up-shoot is, that I was able to install the tmail extension with > Luis' installer recipe ahm, you already did. > If *anybody* has an idea how to tackle the problem of redistributing > extensions, I'd be grateful as heck. Well, Luis Lavena's work is promising. It's time for extension developers to try this environment and make the changes needed. After that, anybody would be able to automatically download and build extensions. -- Gerardo Santana