Loading ...
Sorry, an error occurred while loading the content.

69983Re: [PATCH] Fix compilation failure with Ruby 2.0.0

Expand Messages
  • skeept
    May 21 2:40 PM
    • 0 Attachment
      >
      > > Was this patch applied already?
      >
      > >
      >
      > > I tried compiling a 64 bit windows but if failed complaining that some
      >
      > > include file could not be found.
      >
      > >
      >
      > > If possible could this patch be included for the next release?
      >
      >
      >
      > AFAIK this was included in patch 7.3.889.
      >

      Well, I have downloaded the 64 bit 2.0-p195 rubyinstaller from http://rubyinstaller.org/downloads/
      and configured ruby with
      RUBY="C:\htemp\Ruby200-x64" DYNAMIC_RUBY=yes RUBY_VER=20 RUBY_VER_LONG=2.0.0 ^

      when compiling I get the error:
      c:\htemp\ruby200-x64\include\ruby-2.0.0\ruby/ruby.h(24) : fatal error C1083: Cannot open include file: 'ruby/c
      onfig.h': No such file or directory
      NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\x86_amd64\cl.EXE"' : r
      eturn code '0x2'
      Stop.

      if I don't include the configuration for ruby then I can compile fine (Included patches 1-944).

      Is there a different installer I should be using or different configuration options?


      >
      >
      > > A small example on how to use rubydo (similar to the example on how to
      >
      > > use perldo) would be useful for people like me, that don't know much
      >
      > > about ruby but would like to learn.
      >
      > >
      >
      > > Also for the next release, if possible would it be possible to
      >
      > > distribute a 64 bit for windows as well a 32 bit?
      >
      >
      >
      > It's not all that useful. It uses more memory, is probably a bit
      >
      > slower. I haven't heard real practical advantages. But perhaps that
      >
      > changed with Windows 8?
      >

      I am not sure how much bigger the memory usage will be, but I would not think it would be that big.
      64 bit windows users will probably already use 64 bit python and perl so if there is a 64 bit vim they won't have to install additional 32 bit versions.

      Jorge

      --
      --
      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

      ---
      You received this message because you are subscribed to the Google Groups "vim_dev" group.
      To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
    • Show all 14 messages in this topic