[Graham Bloice <graham.bloice@xxxxxxxxxxxxx>]

On 11 August 2014 11:51, Anders Broman <anders.broman@xxxxxxxxxxxx> wrote:

Invalid command: Split-Path

!include: error in script: "qt-dll-manifest.nsh" on line 1

Error in script "wireshark.nsi" on line 791 -- aborting creation process

 

qt-dll-manifest.nsh:

 

Split-Path : Cannot bind argument to parameter 'Path' because it is null.

At C:\xxx\trunk\packaging\nsis\windeployqt-to-nsis.ps1:23 char:22

+     $dir = Split-Path <<<<  -Parent $entry

    + CategoryInfo          : InvalidData: (:) [Split-Path], ParameterBindingV

   alidationException

    + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,M

   icrosoft.PowerShell.Commands.SplitPathCommand

File "..\..\wireshark-qt-release\"

File /r "..\..\wireshark-qt-release\"

 

Ideas?

 

Regards

Anders

packagins\nsis\Makefile.nmake calls windeployqt-to-nsis.ps1 to create the qt-dll-manifest.nsh file listing all the qt dlls required for the installer.

In the script, windeployqt is called to return the list of DLL's and then on Line 23 of the script calls split-path to get the path component of the DLL.  From the error it seems that one of the entries is null.

Try this:

In a Powershell prompt at your top level source directory:

<code>

$env:Path += ";PATH\TO\QT\BIN"

windeployqt --release --no-compiler-runtime --list relative wireshark-qt-release\qtshark.exe

</code>

--

Graham Bloice