> What kind of level of knowledge are we assuming here? I'm not following you on this one.
WRT the if_ruby.txt mods, I primarily want a Windows user/developer trying to build ruby support into their vim to know there are two primarily flavors of MRI Ruby available for them to check out. I also want to indicate that the RubyInstaller flavor is MinGW build centric (IIRC the other is VC6 32-bit version...haven't looked at the 64-bit version but I think it's VC2008 centric?). While we (RubyInstaller project) get a lot of positive feedback on the ease-of-use benefits, speedier and newer compiler support, etc. I purposely want to stay away from the GCC vs. CL debate as I think it's a red herring. People are building MRI Ruby and vim with different toolchains and I think that's fantastic. However, I'd also like to indicate to a Windows developer building vim from source using a MinGW toolchain and interested in Ruby, that there's an MinGW-based MRI Ruby he or she should check out. FWIW, every time there's a gVim update I do something like the following and build a fresh copy with the MinGW based llvm-gcc v2.8: hg qpop -a && hg pull -u && hg qpush -a && cd src mingw32-make -f Make_mingw.mak gvim.exe CC=llvm-gcc xcopy gvim.exe \vim\vim73 /U So far, so good :) > One thing I found confusing at the start with compiling vim with ruby, > is that while msvc compilation only works against ruby-mswin headers > and vice-versa with mingw, that isn't the case when it comes to > _running_ it, and indeed you can compile with msvc against mingw ruby > by grafting on the mswin ruby headers from the ruby-lang links, and > vice-versa. Ah, I vaguely remember our earlier discussion now. The last time I built vim with dynamic ruby support I don't remember having header difficulties. But then again I only tried building using the standard headers from http://github.com/ruby/ruby and not the config you mention. Sounds like I really need to double check that vim + dynamic Ruby 1.9.2 still builds OK with a MinGW toolchain on Windows 7 and loads the RubyInstaller built Ruby DLL OK. That said, do you think if_ruby.txt still needs some more info to allow one to easily build vim + dynamic ruby on Windows using their favorite toolchain? Jon -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
