Are you using SetEnv.cmd from the SDK? If so, there shouldn’t be any need to then call either vcvarsxxx.bat, SetEnv will do it all.
The approach, I’ve used for many years, is to make sure you have an SDK installed (which has other benefits such as bug fixes, newer compilers and libraries etc., and then use the SetEnv.cmd from the SDK, passing in the appropriate architecture parameter, e.g. “SetEnv /x86” or “SetEnv /x64”.
I don’t think I would recommend using the same source directory, it means having to run distclean and then modify config.nmake when you swap over. Hopefully when I can find time to get into CMake and we can do out of tree builds all that will just go away.
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Beth
Sent: 09 May 2012 22:14
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Building 64 vs. 32-bit question
OK it took me all day, but I have now successfully built wireshark for x64 *and* x86
on a 64-bit PC. (Just not at the same time; I'm reusing the same source folder for now.)
For anyone else migrating from WinXP/32-bit to Win7/64-bit, the main thing you have
to make sure to get right is your environment setup, NOT necessarily anything in the
My personal "wireshark env setup" script calls SetEnv.cmd and a vcvars script to set
things up. Both of those scripts take an argument, x64 or x86. What works for me
is to call SetEnv.cmd with the right argument, then call *either* vcvarsall.bat (for x64)
*or* vcvars32.bat (for x86) with the same argument. Note that the two vcvars scripts
have slightly different paths.
I did a distclean, then a setup, then another distclean, before building all. Not certain
all of these steps are 100% necessary, but the net result was a successful build.