[Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
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 ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] How to support wireshark w/o having an OpenID
On Aug 10, 2014, at 21:43, Ed Beroset bero...@mindspring.com wrote: -Original Message- From: Kevin Cox kevin...@kevincox.ca Sent: Aug 9, 2014 4:05 PM To: Developer support list for Wireshark wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] How to support wireshark w/o having an OpenID On 09/08/14 12:51, Toralf Förster wrote: My question is rather, whether it is mandatory to register at one of the big IT players or if an email address would be sufficient. You don't need to register at one of the big IT players, I think that Wireshark gerrit is set up to accept any OpenID provider. However I believe you are asking if you can sign up with just an email and I'm pretty sure the answer is no because gerrit doesn't do its own authentication. Basically the story is—as currently set up—you need an OpenID but who your provider is doesn't matter, you can use a public service or set your own up but it has to be OpenID. Sorry if that doesn't suit you, maybe you could start a discussion about alternate authentication methods however gerrit doesn't support much.[0] [0] https://gerrit.googlecode.com/svn/documentation/2.1/config-gerrit.html#auth I'm not sure it matters sufficiently that it could or should cause course alteration, but as one who has contributed modestly to Wireshark before the move to gerrit, but not since then, I'd have to say that for me, the setup/registration/configuration/etc. has definitely impeded further contributions. The new process is something that I haven't really gotten around to trying to figure out. I'm not saying it's the wrong choice, but it's just that much more effort to even *submit* a patch, that I suspect that a lot of would-be contributors might find the threshold too high. Maybe updating documentation could help. Right now, if you go to the main develop page https://www.wireshark.org/develop.html and click on the link under code review site you get to https://code.wireshark.org/review/#/q/status:open,n,z which offers no clue at all as to how one should actually register. I'm sure I could figure it out, and I'm sure many have. It's just that I'd really just like to be able to contribute patches without having to do quite so much exploration. Maybe I'm just lazy, but it might be nice if the barrier to useful contribution were lowered just a bit. There is http://wiki.wireshark.org/Development/SubmittingPatches which we should definitely do a better job of advertising. That should walk you through the major setup steps. Where would be a more useful/obvious place to include that information? Evan ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
2014-08-11 12:51 GMT+02:00 Anders Broman anders.bro...@ericsson.com: 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 wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] How to support wireshark w/o having an OpenID
On Mon, Aug 11, 2014 at 1:16 PM, Evan Huus eapa...@gmail.com wrote: On Aug 10, 2014, at 21:43, Ed Beroset bero...@mindspring.com wrote: -Original Message- From: Kevin Cox kevin...@kevincox.ca Sent: Aug 9, 2014 4:05 PM To: Developer support list for Wireshark wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] How to support wireshark w/o having an OpenID On 09/08/14 12:51, Toralf Förster wrote: My question is rather, whether it is mandatory to register at one of the big IT players or if an email address would be sufficient. You don't need to register at one of the big IT players, I think that Wireshark gerrit is set up to accept any OpenID provider. However I believe you are asking if you can sign up with just an email and I'm pretty sure the answer is no because gerrit doesn't do its own authentication. Basically the story is—as currently set up—you need an OpenID but who your provider is doesn't matter, you can use a public service or set your own up but it has to be OpenID. Sorry if that doesn't suit you, maybe you could start a discussion about alternate authentication methods however gerrit doesn't support much.[0] [0] https://gerrit.googlecode.com/svn/documentation/2.1/config-gerrit.html#auth I'm not sure it matters sufficiently that it could or should cause course alteration, but as one who has contributed modestly to Wireshark before the move to gerrit, but not since then, I'd have to say that for me, the setup/registration/configuration/etc. has definitely impeded further contributions. The new process is something that I haven't really gotten around to trying to figure out. I'm not saying it's the wrong choice, but it's just that much more effort to even *submit* a patch, that I suspect that a lot of would-be contributors might find the threshold too high. Maybe updating documentation could help. Right now, if you go to the main develop page https://www.wireshark.org/develop.html and click on the link under code review site you get to https://code.wireshark.org/review/#/q/status:open,n,z which offers no clue at all as to how one should actually register. I'm sure I could figure it out, and I'm sure many have. It's just that I'd really just like to be able to contribute patches without having to do quite so much exploration. Maybe I'm just lazy, but it might be nice if the barrier to useful contribution were lowered just a bit. There is http://wiki.wireshark.org/Development/SubmittingPatches which we should definitely do a better job of advertising. That should walk you through the major setup steps. Where would be a more useful/obvious place to include that information? After The Developer's Guide has complete documentation on preparing and uploading patches. On https://www.wireshark.org/develop.html ? Evan ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Pascal Quantin Sent: den 11 augusti 2014 13:46 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 2014-08-11 12:51 GMT+02:00 Anders Broman anders.bro...@ericsson.commailto:anders.bro...@ericsson.com: 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. PS C:\wireshark-git $PSVersionTable.PSVersion Major Minor Build Revision - - - 2 0 -1 -1 PS C:\wireshark-git Split-Path PS C:\wireshark-git Split-Path cmdlet Split-Path at command pipeline position 1 Supply values for the following parameters: Path[0]: some\path\string\foo\bar Path[1]: some\path\string\ Path[2]: some\path\string\foo some\path PS C:\wireshark-git /Anders ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.com 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 ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice Sent: den 11 augusti 2014 14:04 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.commailto:anders.bro...@ericsson.com 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 Hi, Not sure I got I right: C:\xxx\trunkpowershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. PS C:\xxx\trunk $env:path+=C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin PS C:\xxx\trunk windeployqt --release --no-compiler-runtime --list relative wireshark-qt-release\qtshark.exe The term 'windeployqt' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:12 + windeployqt --release --no-compiler-runtime --list relative wireshark-q t-release\qtshark.exe + CategoryInfo : ObjectNotFound: (windeployqt:String) [], Command NotFoundException + FullyQualifiedErrorId : CommandNotFoundException Just running the command without parameters and the full path gives PS C:\xxx\trunk C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin\windeployqt.exe Please specify the binary or folder. Usage: C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin\windeployqt.exe [options] [file] Qt Deploy Tool 5.2.1 Options: -?, -h, --helpDisplays this help. -v, --version Displays version information. --dir directory Use directory instead of binary directory. --libdir path Copy libraries to path. --force Force updating files. --no-plugins Skip plugin deployment. --no-librariesSkip library deployment. --qmldir directory Scan for QML-imports starting from directory. --no-quick-import Skip deployment of Qt Quick imports. --no-translations Skip deployment of translations. --no-system-d3d-compiler Skip deployment of the system D3D compiler. --webkit2 Deployment of WebKit2 (web process). --no-webkit2 Skip deployment of WebKit2. --jsonPrint to stdout in JSON format. --verbose level Verbose level. --bluetooth Add Qt5Bluetooth module. --no-bluetoothRemove Qt5Bluetooth module. --clucene Add Qt5CLucene module. --no-clucene Remove Qt5CLucene module. --concurrent Add Qt5Concurrent module. --no-concurrent Remove Qt5Concurrent module. Qt libraries can be added by passing their name (-xml) or removed by passing the name prepended by --no- (--no-xml). Available libraries: bluetooth clucene concurrent core declarative designercomponents designer gui clucene qthelp multimedia multimediawidgets network nfc opengl positioning printsupport qml quick quickparticles script scripttools sensors serialport sql svg test widgets winextras xml xmlpatterns webkit Arguments: [file]Binary or directory containing the binary. /Anders ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
On Mon, Aug 11, 2014 at 2:45 PM, Anders Broman anders.bro...@ericsson.com wrote: From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice Sent: den 11 augusti 2014 14:04 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.com 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 Hi, Not sure I got I right: C:\xxx\trunkpowershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. PS C:\xxx\trunk $env:path+=C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin PS C:\xxx\trunk windeployqt --release --no-compiler-runtime --list relative wireshark-qt-release\qtshark.exe The term 'windeployqt' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:12 + windeployqt --release --no-compiler-runtime --list relative wireshark-q t-release\qtshark.exe + CategoryInfo : ObjectNotFound: (windeployqt:String) [], Command NotFoundException + FullyQualifiedErrorId : CommandNotFoundException Just running the command without parameters and the full path gives PS C:\xxx\trunk C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin\windeployqt.exe Please specify the binary or folder. Usage: C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin\windeployqt.exe [options] [file] Qt Deploy Tool 5.2.1 Options: -?, -h, --helpDisplays this help. -v, --version Displays version information. --dir directory Use directory instead of binary directory. --libdir path Copy libraries to path. --force Force updating files. --no-plugins Skip plugin deployment. --no-librariesSkip library deployment. --qmldir directory Scan for QML-imports starting from directory. --no-quick-import Skip deployment of Qt Quick imports. --no-translations Skip deployment of translations. --no-system-d3d-compiler Skip deployment of the system D3D compiler. --webkit2 Deployment of WebKit2 (web process). --no-webkit2 Skip deployment of WebKit2. --jsonPrint to stdout in JSON format. --verbose level Verbose level. --bluetooth Add Qt5Bluetooth module. --no-bluetoothRemove Qt5Bluetooth module. --clucene Add Qt5CLucene module. --no-clucene Remove Qt5CLucene module. --concurrent Add Qt5Concurrent module. --no-concurrent Remove Qt5Concurrent module. Qt libraries can be added by passing their name (-xml) or removed by passing the name prepended by --no- (--no-xml). Available libraries: bluetooth clucene concurrent core declarative designercomponents designer gui clucene qthelp multimedia multimediawidgets network nfc opengl positioning printsupport qml quick quickparticles script scripttools sensors serialport sql svg test widgets winextras xml xmlpatterns webkit Arguments: [file]Binary or directory containing the binary. There is no some issue with Qt 5.2.x ? and windeployqt ? /Anders ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe:
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
2014-08-11 15:02 GMT+02:00 Alexis La Goutte alexis.lagou...@gmail.com: On Mon, Aug 11, 2014 at 2:45 PM, Anders Broman anders.bro...@ericsson.com wrote: From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice Sent: den 11 augusti 2014 14:04 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.com 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 Hi, Not sure I got I right: C:\xxx\trunkpowershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. PS C:\xxx\trunk $env:path+=C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin PS C:\xxx\trunk windeployqt --release --no-compiler-runtime --list relative wireshark-qt-release\qtshark.exe The term 'windeployqt' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:12 + windeployqt --release --no-compiler-runtime --list relative wireshark-q t-release\qtshark.exe + CategoryInfo : ObjectNotFound: (windeployqt:String) [], Command NotFoundException + FullyQualifiedErrorId : CommandNotFoundException Just running the command without parameters and the full path gives PS C:\xxx\trunk C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin\windeployqt.exe Please specify the binary or folder. Usage: C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin\windeployqt.exe [options] [file] Qt Deploy Tool 5.2.1 Options: -?, -h, --helpDisplays this help. -v, --version Displays version information. --dir directory Use directory instead of binary directory. --libdir path Copy libraries to path. --force Force updating files. --no-plugins Skip plugin deployment. --no-librariesSkip library deployment. --qmldir directory Scan for QML-imports starting from directory. --no-quick-import Skip deployment of Qt Quick imports. --no-translations Skip deployment of translations. --no-system-d3d-compiler Skip deployment of the system D3D compiler. --webkit2 Deployment of WebKit2 (web process). --no-webkit2 Skip deployment of WebKit2. --jsonPrint to stdout in JSON format. --verbose level Verbose level. --bluetooth Add Qt5Bluetooth module. --no-bluetoothRemove Qt5Bluetooth module. --clucene Add Qt5CLucene module. --no-clucene Remove Qt5CLucene module. --concurrent Add Qt5Concurrent module. --no-concurrent Remove Qt5Concurrent module. Qt libraries can be added by passing their name (-xml) or removed by passing the name prepended by --no- (--no-xml). Available libraries: bluetooth clucene concurrent core declarative designercomponents designer gui clucene qthelp multimedia multimediawidgets network nfc opengl positioning printsupport qml quick quickparticles script scripttools sensors serialport sql svg test widgets winextras xml xmlpatterns webkit Arguments: [file]Binary or directory containing the
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
2014-08-11 15:07 GMT+02:00 Pascal Quantin pascal.quan...@gmail.com: 2014-08-11 15:02 GMT+02:00 Alexis La Goutte alexis.lagou...@gmail.com: On Mon, Aug 11, 2014 at 2:45 PM, Anders Broman anders.bro...@ericsson.com wrote: From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice Sent: den 11 augusti 2014 14:04 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.com 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 Hi, Not sure I got I right: C:\xxx\trunkpowershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. PS C:\xxx\trunk $env:path+=C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin PS C:\xxx\trunk windeployqt --release --no-compiler-runtime --list relative wireshark-qt-release\qtshark.exe The term 'windeployqt' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:12 + windeployqt --release --no-compiler-runtime --list relative wireshark-q t-release\qtshark.exe + CategoryInfo : ObjectNotFound: (windeployqt:String) [], Command NotFoundException + FullyQualifiedErrorId : CommandNotFoundException Just running the command without parameters and the full path gives PS C:\xxx\trunk C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin\windeployqt.exe Please specify the binary or folder. Usage: C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin\windeployqt.exe [options] [file] Qt Deploy Tool 5.2.1 Options: -?, -h, --helpDisplays this help. -v, --version Displays version information. --dir directory Use directory instead of binary directory. --libdir path Copy libraries to path. --force Force updating files. --no-plugins Skip plugin deployment. --no-librariesSkip library deployment. --qmldir directory Scan for QML-imports starting from directory. --no-quick-import Skip deployment of Qt Quick imports. --no-translations Skip deployment of translations. --no-system-d3d-compiler Skip deployment of the system D3D compiler. --webkit2 Deployment of WebKit2 (web process). --no-webkit2 Skip deployment of WebKit2. --jsonPrint to stdout in JSON format. --verbose level Verbose level. --bluetooth Add Qt5Bluetooth module. --no-bluetoothRemove Qt5Bluetooth module. --clucene Add Qt5CLucene module. --no-clucene Remove Qt5CLucene module. --concurrent Add Qt5Concurrent module. --no-concurrent Remove Qt5Concurrent module. Qt libraries can be added by passing their name (-xml) or removed by passing the name prepended by --no- (--no-xml). Available libraries: bluetooth clucene concurrent core declarative designercomponents designer gui clucene qthelp multimedia multimediawidgets network nfc opengl positioning printsupport qml quick quickparticles script scripttools sensors serialport sql svg test widgets winextras xml xmlpatterns webkit
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
On 11 August 2014 13:45, Anders Broman anders.bro...@ericsson.com wrote: *From:* wireshark-dev-boun...@wireshark.org [mailto: wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice *Sent:* den 11 augusti 2014 14:04 *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.com 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 Hi, Not sure I got I right: C:\xxx\trunkpowershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. PS C:\xxx\trunk $env:path+=C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin Looks like you've missed the ; path separator that should be at the front of the string. Start with a new PS prompt (as you've broken the path in that one) and try again. I'd really like to see what that 5.2.1 windeployqt gives out, but as the others have said, windeployqt in 5.3.x looks to be broken. -- Graham Bloice Software Developer Trihedral UK Limited ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] How to support wireshark w/o having an OpenID
Evan Huus wrote: On Aug 10, 2014, at 21:43, Ed Beroset wrote: I'm not sure it matters sufficiently that it could or should cause course alteration, but as one who has contributed modestly to Wireshark before the move to gerrit, but not since then, I'd have to say that for me, the setup/registration/configuration/etc. has definitely impeded further contributions. The new process is something that I haven't really gotten around to trying to figure out. I'm not saying it's the wrong choice, but it's just that much more effort to even *submit* a patch, that I suspect that a lot of would-be contributors might find the threshold too high. Maybe updating documentation could help. Right now, if you go to the main develop page https://www.wireshark.org/develop.html and click on the link under code review site you get to https://code.wireshark.org/review/#/q/status:open,n,z which offers no clue at all as to how one should actually register. I'm sure I could figure it out, and I'm sure many have. It's just that I'd really just like to be able to contribute patches without having to do quite so much exploration. Maybe I'm just lazy, but it might be nice if the barrier to useful contribution were lowered just a bit. There is http://wiki.wireshark.org/Development/SubmittingPatches which we should definitely do a better job of advertising. That should walk you through the major setup steps. Where would be a more useful/obvious place to include that information? If there were a link to that page, perhaps under the words contribute change, on https://www.wireshark.org/develop.html I think it would be a little easier to find. Also, the sign in step seems to have been the source of most of the questions I've seen on this list, so maybe a bit of expansion on the options there and how to effect them would be useful. I keep thinking that I'll write it up myself once I figure it out, but hadn't gotten around to doing either yet. :( Ed ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice Sent: den 11 augusti 2014 15:18 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 13:45, Anders Broman anders.bro...@ericsson.commailto:anders.bro...@ericsson.com wrote: From: wireshark-dev-boun...@wireshark.orgmailto:wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.orgmailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice Sent: den 11 augusti 2014 14:04 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.commailto:anders.bro...@ericsson.com 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 Hi, Not sure I got I right: C:\xxx\trunkpowershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. PS C:\xxx\trunk $env:path+=C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin Looks like you've missed the ; path separator that should be at the front of the string. Start with a new PS prompt (as you've broken the path in that one) and try again. I'd really like to see what that 5.2.1 windeployqt gives out, but as the others have said, windeployqt in 5.3.x looks to be broken. Argh, Yes of course: PS C:\xxx\trunk $env:path+=;C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin PS C:\xxx\trunk windeployqt --release --no-compiler-runtime --list rela tive wireshark-qt-release\qtshark.exe Unknown options: release, no-compiler-runtime, list. So now we are getting to the problem Alexis pointed out; windeployqt does not have the same parameter sets in Qt 5.2.1 ...). or simply upgrade to Qt 5.3 :) Last time I checked there was no Qt 5.3 for MSVC 2012, MSVC 2013 requires IE version(something) which I don’t have and I have a company Win7 version which I can’t (easily any way) influence the version of the components… Regards Anders ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
On 11 August 2014 15:21, Anders Broman anders.bro...@ericsson.com wrote: *From:* wireshark-dev-boun...@wireshark.org [mailto: wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice *Sent:* den 11 augusti 2014 15:18 *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 13:45, Anders Broman anders.bro...@ericsson.com wrote: *From:* wireshark-dev-boun...@wireshark.org [mailto: wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice *Sent:* den 11 augusti 2014 14:04 *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.com 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 Hi, Not sure I got I right: C:\xxx\trunkpowershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. PS C:\xxx\trunk $env:path+=C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin Looks like you've missed the ; path separator that should be at the front of the string. Start with a new PS prompt (as you've broken the path in that one) and try again. I'd really like to see what that 5.2.1 windeployqt gives out, but as the others have said, windeployqt in 5.3.x looks to be broken. Argh, Yes of course: PS C:\xxx\trunk $env:path+=;C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin PS C:\xxx\trunk windeployqt --release --no-compiler-runtime --list rela tive wireshark-qt-release\qtshark.exe Unknown options: release, no-compiler-runtime, list. So now we are getting to the problem Alexis pointed out; windeployqt does not have the same parameter sets in Qt 5.2.1 ...). or simply upgrade to Qt 5.3 :) Last time I checked there was no Qt 5.3 for MSVC 2012, MSVC 2013 requires IE version(something) which I don’t have and I have a company Win7 version which I can’t (easily any way) influence the version of the components… Yes, I think for Qt 5.3 we need to fallback to some other scheme, i.e. a hard-coded list of DLL's. Maybe you could compile Qt 5.3.1 yourself to get a VS2012 compatible version :-) -- Graham Bloice Software Developer Trihedral UK Limited ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] building a Gtk2 RPM (Was: QT_MIN_VERSION)
On 08/08/14 12:14, Maynard, Chris wrote: -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev- boun...@wireshark.org] On Behalf Of Michal Labedzki Sent: Friday, August 08, 2014 1:46 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] QT_MIN_VERSION I use instead of styleName() and everything seems to be ok. What about use conditional define with QT version? However I vote for update to 4.8.0 I would prefer not to do this, if at all possible, until at least the end of the RHEL6 Production 1 Phase. _https://access.redhat.com/support/policy/updates/errata_ Currently we don't necessarily have any particular need or desire to deploy qtshark on these systems; however: 1) Others may want to? Others will surely want to once 2.0 comes out (where Qt becomes the main/default interface) so +1 from me. (Anyway this was already fixed.) 2) I'm unable to create .rpm's using --without-qt. (or with both --without-gtk2 and --without-gtk3 for that matter, but that hasn’t been a problem since I just don’t bother installing the gnome rpm that’s generated.) RHEL6 doesn't have GTK3, so I’m forced to use, at a minimum, --with-gtk2, and of course change wireshark.spec.in as well: %bcond_withgtk2 %bcond_without gtk3 %bcond_without qt When you're building from the source tree the RPM generation should follow your ./configure options. So: % ./configure --with-gtk2 make rpm-package should do the trick. It seems that some work is still needed to allow a no-GUI RPM build though (in r53607 I said it worked but it doesn't seem to now). Note that the %bcond_with* macros are funny; they don't really do what you'd expect: https://lists.fedoraproject.org/pipermail/devel/2011-December/160357.html ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
On 8/11/14 7:53 AM, Graham Bloice wrote: On 11 August 2014 15:21, Anders Broman anders.bro...@ericsson.com mailto:anders.bro...@ericsson.com wrote: __ __ __ __ *From:*wireshark-dev-boun...@wireshark.org mailto:wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org mailto:wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice *Sent:* den 11 augusti 2014 15:18 *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 __ __ On 11 August 2014 13:45, Anders Broman anders.bro...@ericsson.com mailto:anders.bro...@ericsson.com wrote: *From:*wireshark-dev-boun...@wireshark.org mailto:wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org mailto:wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice *Sent:* den 11 augusti 2014 14:04 *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.com mailto:anders.bro...@ericsson.com 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 Hi, Not sure I got I right: C:\xxx\trunkpowershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. PS C:\xxx\trunk $env:path+=C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin __ __ Looks like you've missed the ; path separator that should be at the front of the string. Start with a new PS prompt (as you've broken the path in that one) and try again. __ __ I'd really like to see what that 5.2.1 windeployqt gives out, but as the others have said, windeployqt in 5.3.x looks to be broken. __ __ Argh, Yes of course: __ __ PS C:\xxx\trunk $env:path+=;C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin PS C:\xxx\trunk windeployqt --release --no-compiler-runtime --list rela tive wireshark-qt-release\qtshark.exe Unknown options: release, no-compiler-runtime, list. __ __ So now we are getting to the problem Alexis pointed out; windeployqt does not have the same parameter sets in Qt 5.2.1 ...). or simply upgrade to Qt 5.3 :) Last time I checked there was no Qt 5.3 for MSVC 2012, MSVC 2013 requires IE version(something) which I don’t have and I have a company Win7 version which I can’t (easily any way) influence the version of the components… __ __ Yes, I think for Qt 5.3 we need to fallback to some other scheme, i.e. a hard-coded list of DLL's. Is there a way to get nmake to compare version strings? We can get the Qt version easily enough using `qmake -query QT_VERSION`. Otherwise we'll probably have to add more DLL checks to packaging/nsis/Makefile.nmake. According to the release notes Qt5WebSockets.dll was added in 5.3. Although I
Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012
On 11 August 2014 17:19, Gerald Combs ger...@wireshark.org wrote: On 8/11/14 7:53 AM, Graham Bloice wrote: On 11 August 2014 15:21, Anders Broman anders.bro...@ericsson.com mailto:anders.bro...@ericsson.com wrote: __ __ __ __ *From:*wireshark-dev-boun...@wireshark.org mailto:wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org mailto:wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice *Sent:* den 11 augusti 2014 15:18 *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 __ __ On 11 August 2014 13:45, Anders Broman anders.bro...@ericsson.com mailto:anders.bro...@ericsson.com wrote: *From:*wireshark-dev-boun...@wireshark.org mailto:wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org mailto:wireshark-dev-boun...@wireshark.org] *On Behalf Of *Graham Bloice *Sent:* den 11 augusti 2014 14:04 *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] Error when running nmake -f makefile.nmake packaging on win7 64 with MSVC 2012 On 11 August 2014 11:51, Anders Broman anders.bro...@ericsson.com mailto:anders.bro...@ericsson.com 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 Hi, Not sure I got I right: C:\xxx\trunkpowershell Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. PS C:\xxx\trunk $env:path+=C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin __ __ Looks like you've missed the ; path separator that should be at the front of the string. Start with a new PS prompt (as you've broken the path in that one) and try again. __ __ I'd really like to see what that 5.2.1 windeployqt gives out, but as the others have said, windeployqt in 5.3.x looks to be broken. __ __ Argh, Yes of course: __ __ PS C:\xxx\trunk $env:path+=;C:\Qt\Qt5.2.1\5.2.1\msvc2012_64\bin PS C:\xxx\trunk windeployqt --release --no-compiler-runtime --list rela tive wireshark-qt-release\qtshark.exe Unknown options: release, no-compiler-runtime, list. __ __ So now we are getting to the problem Alexis pointed out; windeployqt does not have the same parameter sets in Qt 5.2.1 ...). or simply upgrade to Qt 5.3 :) Last time I checked there was no Qt 5.3 for MSVC 2012, MSVC 2013 requires IE version(something) which I don’t have and I have a company Win7 version which I can’t (easily any way) influence the version of the components… __ __ Yes, I think for Qt 5.3 we need to fallback to some other scheme, i.e. a hard-coded list of DLL's. Is there a way to get nmake to compare version strings? We can get the Qt version easily enough using `qmake
Re: [Wireshark-dev] Is PowerShell now a requirement for Windows builds?
On 8/8/14 2:39 AM, Graham Bloice wrote: As Gerald says, I'm not sure how many devs are building on Vista and while we're not (currently) aiming to cast them adrift, they should think about a move to at least Win 7. On a Vista machine here PowerShell 2.0 is installed with no option to uninstall it. I'm not sure how common this is but apparently it can happen as a result of a service pack upgrade. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
