On 20/01/2011 21:26, Dietfrid Mali wrote:
>
> I could as well analyze the automake hell Wireshark comes with. ^_^
> Btw, I would have happily used the Wireshark VS solution to see how to add
> spandsp codecs, but to my horror I found out that it used some nmake hell
> just as well ... and required bash (Cygwin/mingw?) which I don't have
> installed on my Windows machine (why should I).
>
If you take the time to setup a Windows build environment (basically Cygwin +
Python + VS), then you can use the Visual Studio debugger.  Note that
Wireshark is still built using nmake rather than a VS project but VS can
attach to the process to debug it.

The reason that the windows build still uses other tools and nmake is that
no-one has found the time and motivation to create, and most importantly
maintain, a VS solution for Wireshark.

-- 
Regards,

Graham Bloice

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to