From: Harold Hausman Date: 2007-04-27T23:39:07+09:00 Subject: Building one-click installer compatible C extensions on windows with VS2005 Hi. I had an idea for a quick C extension and thought I'd see what it was like to build one. I'm pretty familiar with readme.ext as I've done some things embedding Ruby recently that have all gone splendidly. However, when I tried first to build my new extension using nmake on a makefile generated by my extconf.rb I was greeted with lovely errors about my MSC_VER being unmatch. :D I've read about this before on the various threads that pop up on this list from time to time, but just now I think I'm coming to understand the pain. I circumvented the various MSC_VER checks, and got my extension to build, but unsurprisingly, when I try to require it into a script, I see this: --------------------------- Microsoft Visual C++ Runtime Library --------------------------- Runtime Error! Program: c:\ruby\bin\ruby.exe R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. --------------------------- OK --------------------------- Yay! So I can only imagine that the maintainers of the one-click installer are very happy with their current setup, and I can't really blame them, it's pretty rad and has worked perfectly for me up until this point. (: Various googling and reading hasn't really given me the info I need, so I have a couple quick questions. If the one-click installer did happen to be built with 2005, would I be having this problem? And, what should I do? Is it possible to build one-click-installer compatible C extensions with VS2005? Or do I need to switch to cygwin or MingGW, if so witch? A million thanks for your time, -Harold