[issue1449] make msi work the vs 2005(MSVC8)

Martin v. Löwis report at bugs.python.org
Sun Nov 18 21:53:37 CET 2007


Martin v. Löwis added the comment:

Did you test the change for VS 2003? In my MSMDir
(C:\Programme\Gemeinsame Dateien\Merge Modules), I only have the
following files

GDIPlus.msm
msmask32_X86.msm
msmask32_X86_ENU.msm
VB_Control_mschart_RTL_X86_---.msm
VB_Control_mschart_RTL_X86_ENU.msm
VC_User_ATL71_RTL_X86_---.msm
VC_User_CRT71_RTL_X86_---.msm
VC_User_MFC71_Loc_RTL_X86_---.msm
VC_User_MFC71_RTL_X86_---.msm
VC_User_STL71_RTL_X86_---.msm
VJSharpRedist_x86.msm
WMIUTILS_RTL_X86_---.msm
WMI_DECOUPLED_PROVIDER_RTL_X86_---.msm

So at least on my system, the assertion is triggered that the file is
not found.

The other changes look fine. Just in case it isn't clear: you can add a
config.py to your msi directory, to set things like PCBUILD and MSVCR to
the values you like.

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1449>
__________________________________


More information about the Python-bugs-list mailing list