On Thu, 2 Aug 2012, Bram Moolenaar wrote:
I have a new PC with Windows 7 that I want to use to build Vim for
distribution. [...]
Now building with all the interfaces. I installed:
[...]
Ruby 1.9.2 (from www.garbagecollect.jp, see help file)
Rename include dir from 1.9.1 to 1.9.2
Remove check for _MSC_VER from config.h
Copy bin/msvcrt-ruby191.dll to C:\Windows\msvcrt-ruby192.dll
[...]
The Ruby install has 1.9.1 files even though I installed 1.9.2, very
confusing. I just renamed the files.
Possibly important from a packaging perspective:
You shouldn't have to rename the files. Ruby 1.9.2 and 1.9.3 are
"library compatible" with 1.9.1¹. It seems like it'd be a PITA to have
to compile against a specific, non-standard version of Ruby.
The official (MRI) Ruby page points Windows users to:
http://rubyinstaller.org/
However, it's compiled against MinGW. Is that one of the problems
(linking against different runtimes) the garbagecollect.jp version is
avoiding? The help (:help ruby) didn't seem particularly clear as to
why the weird version was required.
--
Best,
Ben
¹:
Ruby 1.9.2 release notes -
http://www.ruby-lang.org/en/news/2010/08/18/ruby-1-9.2-released/
Explanation of 1.9.1 dir w/ 1.9.{2,3} - http://stackoverflow.com/a/8565831/82723
--
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
