Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Building with Visual Studio Professional 2013 ...

From: Richard Sharpe <realrichardsharpe@xxxxxxxxx>
Date: Sun, 27 Apr 2014 15:05:20 -0700
On Sun, Apr 27, 2014 at 1:41 PM, Richard Sharpe
<realrichardsharpe@xxxxxxxxx> wrote:
> On Sun, Apr 27, 2014 at 1:07 PM, Richard Sharpe
> <realrichardsharpe@xxxxxxxxx> wrote:
>> On Sun, Apr 27, 2014 at 12:58 PM, Richard Sharpe
>> <realrichardsharpe@xxxxxxxxx> wrote:
>>> On Sun, Apr 27, 2014 at 12:49 PM, Richard Sharpe
>>> <realrichardsharpe@xxxxxxxxx> wrote:
>>>> On Sun, Apr 27, 2014 at 12:38 PM, Pascal Quantin
>>>> <pascal.quantin@xxxxxxxxx> 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.
>>
>> OK, got much further after installing m4 for Cygwin ... almost there ...
>
> So, now I am stuck on the unresolved externals wrt ett_nds.
>
> I have installed the native Win32 version of Python, but that does not
> seem to have prevented this problem.

Something went wrong with epan\dissectors\packet-ncp.c etc, but after
checking them out again and rebuilding, I seem to have a
wireshark.exe.

However, now I get "The program failed to start because
wiretap-1.11.0.dll is missing ..."

Now. to figure out what to do.

-- 
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)