Wireshark-bugs: [Wireshark-bugs] [Bug 3500] Add Python embedding to Windows makefiles
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3500
--- Comment #34 from Michael Mann <mmann78@xxxxxxxxxxxx> 2011-06-23 13:01:56 PDT ---
(In reply to comment #33)
> Well, I have 2 different Windows laptops, one compiling Wireshark with
> MSVC2008EE and the other with MSVC2010EE. PYTHON_EMBED=1 works with MSVC2008EE
> but not with MSVC2010EE. Wireshark still compiles fine with MSVC2010EE, but
> crashes at startup when you attempt to run it. The Dependency Walker reveals
> that python 2.7.2 (which is the version I'm running on the MSVC2010EE laptop)
> depends on MSVCR90.DLL, file ver 9.0.30729.4974, and I believe that's where the
> problem lies because Wireshark depends on MSVCR100.DLL, file ver. 10.0.40219.1.
> It is my understanding that they both have to be compiled using the same
> version of the compiler.
I have MSVC2008EE so Python 2.7.2 must have been built with MSVC2008EE then?
(I'm not seeing the crash). I just went to the Python download page to grab
the installer and the Windows versions don't include source (so I never tried
to build Python).
Does that mean I have to build the Python DLL with Wireshark to ensure its MSVC
version independence? Does this make it a wireshark-win*-libs candidate?
Or Should config.nmake be modified to only allow PYTHON_EMBED=1 if
MSVC_VARIANT=MSVC2008 because that's what the Windows installer appears to
produce?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
