Hmmm...don't quite know what you mean by "a mingw," but back in April I was able to get RMagick to build with the mingw one-click installer that Luis Lavena has been working on, if that's what you mean.
I used the standard RMagick 2.3.0 source distribution, the MS Visual C++ 2005 Express Edition compiler, and the same ImageMagick Win32 binary installer that the rmagick-win32 gem relies on. (This last is good because it means you don't have to mess around with compiling and building ImageMagick and all its dependent libraries.)
The only change I made was to modify RMagick's extconf.rb file to deal with the fact that the ImageMagick binary installer doesn't install Magick-config. On *nix-installs, Magick-config is a little shell script that the ImageMagick ./configure script creates when you configure ImageMagick for your particular machine. It's similar to Ruby's rbconfig.rb file. RMagick's extconf.rb runs Magick-config to find out things like the directory where ImageMagick's libraries are installed.
Without Magick-config, I had to hack RMagick's extconf.rb to find the ImageMagick libraries, check the ImageMagick version number, etc., on its own. I just poked around in the ImageMagick installation directory until I got it to work on my machine. In a "production" release I'd probably ask the IM developers for a better way to discover that information, but my goal was to determine if I could build RMagick with the mingw oci, not write a "production-quality" installer.
However, I suspect that anybody who is messing with the mingw oci is prepared to hack around a bit, so with that in mind, if you want to give it a try yourself I'll be glad to upload the extconf.rb file I used. Let me know.
|
Start New Thread
RE: mingw [ reply ]