On So, 03 Jul 2016, Ken Takata wrote:
> Hi Christian,
>
> 2016/7/3 Sun 20:09:44 UTC+9 Christian Brabandt wrote:
> > Hi,
> > I have been trying to compile Vim on appveyor against the new 2.7.12
> > python library. As far as I can tell, I setup all needed environment
> > variables
> > set PYTHON_DIR=c:\python2712
> > set PYTHON_VER=27
> > set DYNAMIC_PYTHON=yes
> >
> > And I even put PYTHON_DIR at the beginning of the PATH, so that this
> > python installation will be found before the system wide installation of
> > 2.7.11 in c:\python27
> >
> > Vim compiles and links fine, however, when I issue:
> > python import sys; print sys.version
> > I see this:
> > https://ci.appveyor.com/project/chrisbra/vim-win32-installer-33v6e/build/70/job/bp8929sxxq9ci070#L955
> > 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015, 20:40:30) [MSC v.1500 64 bit
> > (AMD64)]
> >
> > Can someone tell me, how Vim is finding the wrong python27.dll?
>
> The python27.dll is normally installed into C:\Windows\System32 (64 bits) or
> C:\Windows\SysWOW64 (32 bits). If the installer doesn't overwrite the dll,
> it might happen. I'm not sure your installation command does overwrite the
> python27.dll in the system directory.
Ah, I didn't check there.
Well, the installation didn't replace the system python27.dll? Are you
saying I need to replace that one? I tried installing using msiexec /A
but that didn't help. Then I tried replacing
c:\windows\{SysWOW64,system32}\python27.dll and that seems to work.
Not sure, this is worth the trouble for the vim-win32-installer
repository.
Best,
Christian
--
Leben ist die Kunst, taugliche SchluĂfolgerungen aus unzureichenden
Prämissen zu ziehen.
-- Samuel Butler
--
--
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.
