Re: [Wireshark-dev] Build with VS 2013 on Windows 7

2016-12-27 Thread Paul Offord
ct: Re: [Wireshark-dev] Build with VS 2013 on Windows 7 Thanks guys. I'll start by deleting everything and starting from scratch. Sent from Samsung Mobile on O2 Original message From: Graham Bloice Date:26/12/2016 20:23 (GMT+00:00) To: Developer support list for Wireshark Subje

Re: [Wireshark-dev] Build with VS 2013 on Windows 7

2016-12-26 Thread Paul Offord
Thanks guys. I'll start by deleting everything and starting from scratch. Sent from Samsung Mobile on O2 Original message From: Graham Bloice Date:26/12/2016 20:23 (GMT+00:00) To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Build with VS 2013 on Windows

Re: [Wireshark-dev] Build with VS 2013 on Windows 7

2016-12-26 Thread Graham Bloice
On 26 December 2016 at 09:48, Paul Offord wrote: > Hi, > > > > It’s been a few months since I built Wireshark. I’m using the same > machine as I have used for my last successful build. I pulled the latest > Wireshark code and ran the CMAKE command to generate the

Re: [Wireshark-dev] Build with VS 2013 on Windows 7

2016-12-26 Thread Roland Knall
It could be, that the version of Powershell required is not the correct one. Some versions of Windows Server use a version out-of-the-box which is too old for the script to work. Not sure, which version to use, but I'd try to update to the latest one. Another thing could be an improperly cleaned

[Wireshark-dev] Build with VS 2013 on Windows 7

2016-12-26 Thread Paul Offord
Hi, It's been a few months since I built Wireshark. I'm using the same machine as I have used for my last successful build. I pulled the latest Wireshark code and ran the CMAKE command to generate the build files. I get this: C:\Development\wsbuild64>cmake -DENABLE_CHM_GUIDES=on -G "Visual