2014-08-11 12:51 GMT+02:00 Anders Broman <[email protected]>:
> 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 > > Hi Anders, according to http://technet.microsoft.com/en-us/library/hh849809%28v=wps.620%29.aspx, Split-Path should work with PowerShell 2.0 onwards. What do you get when typing $PSVersionTable.PSVersion in PowerShell? On my side I have version 3.0 and the windeployqt-to-nsis.ps1 script works fine. Pascal.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
