Remember that you also have to build all of the extensions and RubyGems because the binaries produced with VC2008 use a different runtime dll than VC6 and you can't mix them without causing problems.<br><br>Curt<br><br>
<div class="gmail_quote">On Jan 11, 2008 8:14 PM, Will Rogers <<a href="mailto:wjrogers@gmail.com">wjrogers@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>There doesn't seem to be any discussion on this list right now, so let<br>me kick something off. I contacted Curt and Luis earlier this week to<br>ask what their plans were with regard to migrating the OCI to a new
<br>compiler. Luis seems to be working on a bootstrapping approach using<br>mingw, which is fine, but I still think that the "best" thing to do<br>would be to build with the Microsoft compiler on Windows, it being the
<br>native solution and all. Also, according to what I've read, linking<br>with the newer versions of the MS C runtime has some advantages in<br>terms of security and stability compared to the old msvcrt.dll that<br>mingw (and vc6) links to.
<br><br>I started trying to build everything necessary for the OCI using<br>VC2005. I quickly realized that finding, installing, updating, and<br>configuring VC2005 Express is a gigantic pain in the ass. It does not<br>work with the Platform SDK out of the box, which means you have to
<br>edit some config files by hand to build win32 applications. This is<br>far from ideal.<br><br>Getting set up with VC2008 Express, however, is easy. You just have to<br>download one file from <a href="http://www.microsoft.com/express/" target="_blank">
http://www.microsoft.com/express/</a> and install<br>it. Everything works out of the box. I also see some advantage to<br>using the latest version (it will probably be available for longer, at<br>the least).<br><br>So, on to the actual compiling.
<br><br>I started with Ruby 1.8.6-p111 and zlib. Both build flawlessly with<br>vc2008. Easy. I continued with openssl, building with NASM 2.00 +<br>vc2008. I had to copy the nasm.exe binary to nasmw.exe for the openssl<br>
makefile to work, but then it also built fine.<br><br>Then I hit readline. Readline is a mess. There isn't really an<br>up-to-date, well-maintained windows port, as far as I can tell. I<br>think there needs to be a reliable port of this library to really
<br>depend on the Microsoft compiler. I'm willing to try to learn how to<br>port it, but I don't really have the existing expertise to do it<br>quickly. If anyone has some ideas or pointers here, I'm all ears.
<br><br>What other dependencies does the OCI have? iconv, tcl?<br><br>I want to be clear that I'm not challenging Luis's work on the<br>mingw-based bootstrapping setup. I think it's valuable to work on both<br>
in parallel, to learn more about what's possible. I will have some<br>time this weekend to work on getting further with the vc2008 builds.<br><br><br>A good night to all,<br><br>- Will<br>_______________________________________________
<br>Rubyinstaller-devel mailing list<br><a href="mailto:Rubyinstaller-devel@rubyforge.org">Rubyinstaller-devel@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/rubyinstaller-devel" target="_blank">http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
</a><br><br><br></blockquote></div><br>