Wireshark · Wireshark-dev: Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

[Graham Bloice <graham.bloice@xxxxxxxxxxxxx>]

returning this to -dev

On 30 March 2016 at 16:53, Robert Cragie <robert.cragie@xxxxxxxxxxxxx> wrote:

It seems to be picking up the Windows installation of Python (which is in the path). Removing this from the path will mess up a lot of things for me as most of the time I do not want to use the cygwin python installation. What concerns me now is that the changes I have made have now broken my nmake build so will probably have to fiddle with the paths again...

Robert

Both pythons are used, the Windows native one directly by the Wireshark build, and the Cygwin one by the asciidoc stuff.  I'm not sure what the issue is with your build environment yet.  I do not use the Cygwin python either and would much rather we didn't require it.  Maybe this announcement (http://www.hanselman.com/blog/DevelopersCanRunBashShellAndUsermodeUbuntuLinuxBinariesOnWindows10.aspx) that MS is making Ubuntu tools available might help in the future.

nmake is much more directly configured via config.nmake so is likely to be more resilient about path issues but does require the correct manual configuration.

Apart from the changes to path which are probably mitigated by the manual configuration in config.nmake you should be able to return to nmake quite easily.

--

Graham Bloice