On Wednesday, 31 December 2014 19:51:20 UTC+1, Steve Hall  wrote:
> On Wed, Dec 31, 2014 at 12:41 PM, Shiny Bling <[email protected]> wrote:
> > 
> > My main reason doing the build is that Vim Windows builds like the
> > above don't include 3rd party dependencies(ruby, python, ...). You
> > have to install them yourself. I needed ruby for some plugin and when
> > I added it, the whole Vim process was crashing. There was also a case,
> > when I downloaded some Vim build and it required Ruby version, which
> > was not yet released at http://rubyinstaller.org/
> 
> 
> You can use the dynamic flags for several dependencies to avoid this.
> My builds use them for these major ones:
> 
> 
>   +gettext/dyn
>   +iconv/dyn
>   +lua/dyn
>   +multi_byte_ime/dyn
>   +perl/dyn
>   +python/dyn
>   +python3/dyn
>   +ruby/dyn

In order for that to work reliably, the end user has to install exact dlls 
which were used during the build. Otherwise, Vim can crash if there are 
compiler ABI incompatibilities(mingw vs Microsoft compiler) or incompatible 
function signature changes in the dlls. Let alone the fact, that the end user 
has to install dlls of languages he might have no idea about only because they 
are required by plugins. I think that for a smooth experience, it should be all 
distributed together. That is how it works in Linux distributions.

> 
> > When I started I thought it would be just a matter of compiling it
> > all but it turned out to be quite long endeavour.
> 
> 
> You've got that right! I maintain a DOS batch script for everything
> from the download/update to the NSIS installer build. Over the years
> it has grown to 1,300 lines!

I can feel your pain ;)

kybu

-- 
-- 
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to