On Tuesday, May 20, 2014 3:16:36 PM UTC+2, Ken Takata wrote:
> Hi,
> 
> 2014/5/20 Tue 2:48:13 UTC+9 Germishuys Jacques wrote:
> > It is really problematic to get python extensions to work on Windows, 
> > mainly due to the fact that the manifest we are providing is not compatible 
> > and/or VIM is built with the static CRT.
> > 
> > This patch embeds the generated manifest file. The existing gvim.exe.mnf 
> > file has been slightly truncated, as it should really not dictate which 
> > assemblies are required. It will still be compiled by the resource 
> > compiler, and should provide the extra info i.e. description and DPI 
> > settings.
> > 
> > The patch was generated by "git format-patch", but should be applyable with 
> > "patch -p1".
> 
> Do you use Python for Windows extensions (pywin32)?  If so, it's a problem of
> pywin32, not Vim, I think.
> http://bugs.python.org/issue7833
> This is caused because pywintypes27.dll doesn't have embedded manifest.
> 
> 
> -  <dependency>
> -    <dependentAssembly>
> -      <assemblyIdentity
> -        type="win32"
> -        name="Microsoft.Windows.Common-Controls"
> -        version="6.0.0.0"
> -        publicKeyToken="6595b64144ccf1df"
> -        language="*"
> -        processorArchitecture="*"
> -      />
> -    </dependentAssembly>
> -  </dependency>
> 
> This part is needed for the visual styles.
> 
> Regards,
> Ken Takata

I'm actually having problem with extensions that load python27.dll (which was 
linked against the multithreaded runtime). You are right about the assembly. 
For some reason I was blind and thought it was the CRT assembly. I've attached 
a new patch that updates the manifest by adding the CRT information. This is 
better (nicer) than having to also put it down with the executable.

-- 
-- 
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.
>From 60e8dac7d8733596492083f7e92376cf99a28579 Mon Sep 17 00:00:00 2001
From: Jacques Germishuys <[email protected]>
Date: Tue, 20 May 2014 22:12:23 +0200
Subject: [PATCH] Embed manifest in binary for multithreaded builds

---
 src/Make_mvc.mak | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/Make_mvc.mak b/src/Make_mvc.mak
index ab02890..4a979e4 100644
--- a/src/Make_mvc.mak
+++ b/src/Make_mvc.mak
@@ -973,6 +973,7 @@ $(VIM).exe: $(OUTDIR) $(OBJ) $(GUI_OBJ) $(OLE_OBJ) $(OLE_IDL) $(MZSCHEME_OBJ) \
 		$(LUA_OBJ) $(MZSCHEME_OBJ) $(PERL_OBJ) $(PYTHON_OBJ) $(PYTHON3_OBJ) $(RUBY_OBJ) \
 		$(TCL_OBJ) $(SNIFF_OBJ) $(CSCOPE_OBJ) $(NETBEANS_OBJ) \
 		$(XPM_OBJ) $(OUTDIR)\version.obj $(LINKARGS2)
+	if exist $(VIM).exe.manifest mt.exe -nologo -manifest $(VIM).exe.manifest -updateresource:$(VIM).exe;1
 
 $(VIM): $(VIM).exe
 
-- 
1.8.1.msysgit.1

Raspunde prin e-mail lui