https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3500
--- Comment #32 from Michael Mann <mmann78@xxxxxxxxxxxx> 2011-06-23 11:51:41 PDT ---
(In reply to comment #31)
> (In reply to comment #30)
> > Created an attachment (id=6512)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6512) [details]
[details]
> > PYTHON_EMBED default support
> >
> > Modified config.h.win32 to accomodate both win32 and win64 support so
> > PYTHOD_EMBED can be enabled by default.
> Shouldn't PYTHON_EMBED=1 only be set if the version of python installed was
> compiled with the same compiler as that configured in config.nmake?
I believe I ran into the problem you're describing, and I'm not sure what the
proper solution is. With MSVC I can build either the 32-bit or 64-bit version
of Wireshark on a 32-bit OS (but I obviously need a 64-bit OS to run the 64-bit
version). However Python 2.7's installer is smart enough to realize which type
of OS its installing to and won't let you install the 64-bit version on a
32-bit system.
To test building 64-bit Wireshark with PYTHON_EMBED=1 (which is where this bug
got stalled), I installed Python 2.7 on a 64-bit OS and copied the lib/dll the
C:\Python27 directory on the 32-bit machine that has my Wireshark
development(saving off the 32-bit versions so I could revert to them). I could
successfully build Wireshark (using patch #6512), but still got a lot of the
ssize_t != int type warnings from building the wireshark-win64-libs source (SVN
source was OK). Since MSVC can build both 32 and 64 bit versions of Wireshark,
perhaps a more eloquent solution is needed in using the correct Python lib
(forcably have 2 copies of Python in different directories and adjust makefiles
accordingly?). Perhaps it was assumed that someone would only build the
version of Wireshark that corresponded to the build PC's OS (so the correct
version of Python would always be available)
--
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.
