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

[Graham Bloice <graham.bloice@xxxxxxxxxxxxx>]

On 26 December 2016 at 09:48, Paul Offord <Paul.Offord@xxxxxxxxxxxx> 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 build files.  I get this:

 

C:\Development\wsbuild64>cmake -DENABLE_CHM_GUIDES=on -G "Visual Studio 12 Win64" ..\wireshark

-- Generating build using CMake 3.3.0

CMake Error at CMakeLists.txt:80 (find_package):

 By not providing "FindPowerShell.cmake" in CMAKE_MODULE_PATH this project

  has asked CMake to find a package configuration file provided by

  "PowerShell", but CMake did not find one.

That's an odd CMake error.

We provide a FindPowerShell.cmake module in the source distribution, so I don't understand why CMake is complaining about not finding one.

 

 

  Could not find a package configuration file provided by "PowerShell" with

  any of the following names:

 

    PowerShellConfig.cmake

    powershell-config.cmake

 

  Add the installation prefix of "PowerShell" to CMAKE_PREFIX_PATH or set

  "PowerShell_DIR" to a directory containing one of the above files.  If

  "PowerShell" provides a separate development package or SDK, be sure it has

  been installed.

And every Windows machine I've seen since Vista has had Powershell on the path, so why it shouldn't be found is also odd.

 

 

-- Configuring incomplete, errors occurred!

See also "C:/Development/wsbuild64/CMakeFiles/CMakeOutput.log".

See also "C:/Development/wsbuild64/CMakeFiles/CMakeError.log".

 

On line 80 of CMakeList.txt it says:

 

   find_package(PowerShell REQUIRED)

 

I can confirm that PowerShell is installed on the PC, but I guess that’s not what this error is indicating.

 

Any advice?

 

Thanks and regards…Paul

Thoughts on the issues:

1. Presumably you've updated the source to latest master and have no local changes?
2. Presumably you're using the same "setup" for the command shell you were using previously?
3. Delete your build directory and run the CMake generation step again (or just delete CMakeCache.txt in the build dir).  This is necessary whenever any of the CMake cached paths to libraries and executables change.
   

Pro tip for Windows Wireshark dev: Use a VM.  This allows you to create and manage the build environment keeping it all just for Wireshark.

--

Graham Bloice