Re: 'could not load library msvcrt-ruby18.dll'

From: BG - Ben Armstrong, Dec 5, 2005 9:31 AM
>
> Even though it bloats the package a bit, would you please consider
> statically linking all languages into the gvim that you ship, or at
> least provide static & dynamic versions of the package?
I'll test to see what this does to file size in the next week or so.
--
Steve Hall [ digitect mindspring com ]
:: Cream...the usability project for Vim
:: http://cream.sf.net

Thread view

From: BG - Ben Armstrong, Dec 5, 2005 9:31 AM
>
> Even though it bloats the package a bit, would you please consider
> statically linking all languages into the gvim that you ship, or at
> least provide static & dynamic versions of the package?
I'll test to see what this does to file size in the next week or so.
--
Steve Hall [ digitect mindspring com ]
:: Cream...the usability project for Vim
:: http://cream.sf.net

On Mon, 2005-12-05 at 13:53 -0500, Steve Hall wrote:
> From: BG - Ben Armstrong, Dec 5, 2005 9:31 AM
> >
> > Even though it bloats the package a bit, would you please consider
> > statically linking all languages into the gvim that you ship, or at
> > least provide static & dynamic versions of the package?
>
> I'll test to see what this does to file size in the next week or so.
Thanks. My workaround is to ship all Ruby/bin/*.dll files in the same
directory as gvim.exe (leaving would-be python/perl scripters in the
lurch, but for the time being we don't have any of those). Also, this
solution probably isn't optimal because I doubt if all of the dlls are
actually needed to make ruby work. Still, I tried just copying the one
that was missing, and that didn't work, so rather than waste time
figuring out which are really needed, I threw them all in.
Ben

On Mon, 2005-12-05 at 14:56 -0400, BG - Ben Armstrong wrote:
> On Mon, 2005-12-05 at 13:53 -0500, Steve Hall wrote:
> > From: BG - Ben Armstrong, Dec 5, 2005 9:31 AM
> > >
> > > Even though it bloats the package a bit, would you please
> > > consider statically linking all languages into the gvim that you
> > > ship, or at least provide static & dynamic versions of the
> > > package?
> >
> > I'll test to see what this does to file size in the next week or so.
Reviving and old thread.
I followed up on compiling static language support and it does not
work, Vim's build process does not currently support it. One of the
developers tried once, but this is an open issue.
Sorry!
--
Steve Hall [ digitect mindspring com ]
:: Cream... something good to put in your Vim!
:: http://cream.sourceforge.net