On Sun, Apr 27, 2014 at 12:49 PM, Richard Sharpe <realrichardsha...@gmail.com> wrote: > On Sun, Apr 27, 2014 at 12:38 PM, Pascal Quantin > <pascal.quan...@gmail.com> wrote: >> MSVC2013 comes with a x64 compiler so you should directly call vcvarsall.bat >> with the x64 parameter, and not call SetEnv.Cmd from the 7.1 SDK. > > Ahhh, that sounds reasonable. I got past the original problem, but > then ran into a problem where SetEnv.Cmd was overriding the INCLUDE > path to something that did not exist. > > Hmmm, but then I run into problems where win32.mak is not found.
Got much further after following the hint here: http://ask.wireshark.org/questions/4725/file-win32mak-not-found-stop Now have a problem with Bison, m4 subprocess failed. -- Regards, Richard Sharpe (何以解憂?唯有杜康。--曹操) ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe