Ken Takata wrote:
> Hi Bram,
>
> 2017/10/16 Mon 0:08:11 UTC+9 Bram Moolenaar wrote:
> > This doesn't work properly. The first problem is that running
> > install.exe gives an error that filetype.vim cannot be found. The code
> > for this didn't change in years:
> >
> > sprintf(buf, "%s\\filetype.vim", installdir);
> > if (stat(buf, &st) < 0)
> > {
> > printf("ERROR: Cannot find filetype.vim in \"%s\"\n", installdir);
> >
> > Is the library we build with, containing stat(), not compatible with XP?
>
> I haven't tried, but it might be possible.
>
>
> > When building install.exe with MSVC 2008 it works again.
> > But then running Vim also appears to not work, the toolbar is missing,
> > for example. Building everything with MSVC 2008 fixes that.
>
> This looks similar to the following problem:
> https://groups.google.com/d/topic/vim_dev/ktON3sSR-zI/discussion
> At that time, stat() returns an error when built by BCC5, and failed to show
> menus, toolbars, etc.
>
>
> > Anyone has an idea of how to make it work on Windows XP with MSVC 2015?
>
> Maybe, there are some options:
>
> 1. Implement our own stat() that can work on WinXP.
> (I don't want to do this, though.)
>
> 2. Back to VC2008, and stop enabling if_tcl in the official installer.
> The reason why we have to use VC2015 is that ActiveTcl 8.6.6 requires it.
> If someone want to use if_tcl, they should use vim-win32-installer instead.
> I think this is the easiest solution.
>
> 3. Back to VC2008. Stop using tclstub86.lib from ActiveTcl 8.6.6 and use one
> built by ourself. I haven't tried this, but hopefully the DLL from
> ActiveTcl 8.6.6 can be used.
> Someone who tried to use VC2017 needed to recompile tcl by himself:
> https://github.com/vim/vim/issues/2127#issuecomment-330505345
>
> 4. Drop support for XP. Maybe, you don't like this. ;-)
There are a few problem reports related to stat() on XP when building
with MSVC 2015. They suggest installing newer files. I did update some
files, but it did not appear to make a difference. Not sure if I
installed the wrong files, didn't register them, or whatever. The MSDN
remarks about this are very vague.
Another option would be to use MSVC 2013, which was reported to still
work. I don't know what the situation is with interfaces then.
I should also try the daily build installer on XP. I'll do that when I
have some time.
--
Veni, Vidi, Video -- I came, I saw, I taped what I saw.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
