[Paul Offord <Paul.Offord@xxxxxxxxxxxx>]

I did this:

 

git fetch origin

git reset --hard origin/master

 

It seems to have fixed the problem.

 

Best regards…Paul

 

From: Wireshark-dev [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Paul Offord
Sent: 17 August 2017 20:14
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] master-2.4 cmake problem

 

Hi Graham,

 

The FindPowerShell.cmake module is not there.  I have the following:

 

 

I wonder if the checkout has not given me a complete source tree.  Is there a “sanity” type git command that would ensure I get all the source?

 

Best regards…Paul

 

From: Wireshark-dev [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Graham Bloice
Sent: 17 August 2017 18:54
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] master-2.4 cmake problem

 

 

 

On 17 August 2017 at 18:35, Paul Offord <Paul.Offord@xxxxxxxxxxxx> wrote:

Hi,

 

I’m getting a problem building master-2.4.  The repro steps are:

 

• Deleted all files in the WS code tree
• Deleted all files in the wsbuild64 directory
• Check out master-2.4.
• Do git pull to refresh
• Run the prep cmake command (as below)
• I get errors complaining about PowerShell

 

 

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

-- The C compiler identification is MSVC 18.0.31101.0

-- The CXX compiler identification is MSVC 18.0.31101.0

-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/x86_amd64/cl.exe

-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/x86_amd64/cl.exe -- works

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/x86_amd64/cl.exe

-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/x86_amd64/cl.exe -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

-- Detecting CXX compile features

-- Detecting CXX compile features - done

-- Generating build using CMake 3.7.2

CMake Error at CMakeLists.txt:78 (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.

 

  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.

 

 

-- Configuring incomplete, errors occurred!

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

 

C:\Development\wsbuild64>

 

 

I did a search and found that Graham B had helped me with the same problem last December but on Windows 7 (I’m now on Windows 10).  This is on a dev VM that I haven’t changed other than last week the VM installed Windows Updates.  I have been building WS on the same VM although I switch branches quite a lot as I have a couple of private local branches.

 

Should I be able to see the file FindPowerShell.cmake in the source tree and if so where?

 

Cheers…Paul

 

 

PowerShell should always be on your Windows path, you really have to go out of your way to get rid of it.

 

The FindPowerShell.cmake module should be in <source_dir>\cmake\modules\

 

It's very simple as powershell.exe should be on your path, usually in<Windir>\System32\WindowsPowerShell\v1.0.

 

 

--

Graham Bloice

______________________________________________________________________

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

______________________________________________________________________

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________