Error R6034 when starting VIM loading Python dynamically under Windows 7

[GoogleCodeExporter]

Under Windows 7 (64 Bit) my VIM builds produce an runtime error R6034 stating 
that an application attempts to use the C Runtime library in an incorrect 
manner. After two such message boxes VIM starts nevertheless but without Python 
support.

So far I understand the reports and solutions in the net about that error the 
root cause is that VIM loads the Python DLL (python27.dll in my case) 
_dynamically_ and Python loads the MSVC runtime DLL without having a correct 
manifest.

reference:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/9fbc9292-11b8-4ee4-94a4-52
23546df280/r6034-attempt-to-load-c-runtime-library-without-using-manifest?forum=
vcgeneral

Original issue reported on code.google.com by ma...@von-oppen.com on 16 Oct 2013 at 4:19

[GoogleCodeExporter]

here for reference the original error message box...

Original comment by ma...@von-oppen.com on 17 Oct 2013 at 7:57

Attachments:

• VIM_Error.png

[GoogleCodeExporter]

There's a workaround for this problem posted @ SO 
http://stackoverflow.com/a/10257098/851055 

Original comment by zaaghad@gmail.com on 6 Feb 2014 at 1:47

[GoogleCodeExporter]

Yes, thanks a lot. It is clear to me that this problem cannot be fixed from VIM 
point of view. It is annoying that I have to use this mt.exe utility on every 
system where I use VIM because on every system may be installed another version 
of the MSVC runtime DLLs.

I have a 3rd party AciveX application which loads the Python DLL and uses a 
different set of MSVC runtime DLLs depending from if it is called from Internet 
Explorer or Firefox. For that application there is no solution at all.

Maybe I should talk to the Python developers if they could provide a Python 
version with MSVC runtime statically linked into the Python DLL.

Original comment by ma...@von-oppen.com on 6 Feb 2014 at 8:29