From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx]
On Behalf Of Graham Bloice On 15 August 2014 14:15, Anders Broman <anders.broman@xxxxxxxxxxxx> wrote: Hi, I get ( Win7 64 and Visual studio 2012 ) :
0 File(s) copied
xcopy ".\pdml2html.xsl" wireshark-gtk2 /d
0 File(s) copied
powershell -executionpolicy bypass -File tools/textify.ps1 -Destination wireshark-gtk2 ./COPYING ./NEWS ./README ./README.windows
Get-ChildItem : A parameter cannot be found that matches parameter name 'File'.
At C:\ewireshark2\trunk\tools\textify.ps1:71 char:42
+ foreach ($src_file in Get-ChildItem -File <<<< $SourceFiles) {
+ CategoryInfo : InvalidArgument: (:) [Get-ChildItem], ParameterB
indingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Comm
ands.GetChildItemCommand
xcopy ".\cfilters" wireshark-gtk2 /d
0 File(s) copied
xcopy ".\colorfilters" wireshark-gtk2 /d
0 File(s) copied
xcopy ".\dfilters" wireshark-gtk2 /d
0 File(s) copied
xcopy ".\smi_modules" wireshark-gtk2 /d
0 File(s) copied
xcopy ".\epan\wslua\init.lua" wireshark-gtk2 /d
0 File(s) copied
xcopy ".\epan\wslua\console.lua" wireshark-gtk2 /d
0 File(s) copied
xcopy ipmap.html wireshark-gtk2 /d
0 File(s) copied
xcopy doc\*.html wireshark-gtk2 /d
0 File(s) copied
if not exist wireshark-gtk2\help mkdir wireshark-gtk2\help
xcopy ".\help\toc" wireshark-gtk2\help /d
0 File(s) copied
powershell -executionpolicy bypass -File tools/textify.ps1 -Destination wireshark-gtk2\help help\*.txt
Get-ChildItem : A parameter cannot be found that matches parameter name 'File'.
At C:\ewireshark2\trunk\tools\textify.ps1:71 char:42
+ foreach ($src_file in Get-ChildItem -File <<<< $SourceFiles) {
+ CategoryInfo : InvalidArgument: (:) [Get-ChildItem], ParameterB
indingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Comm
ands.GetChildItemCommand
ands.GetChildItemCommand : NMAKE : fatal error U1073: don't know how to make '..\..\wireshark-gtk2/help/cap ture_filters.txt' Stop. NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0 \VC\BIN\nmake.exe"' : return code '0x2' Stop. Any ideas? On Win7 x64 (VS2013 but that shouldn't matter for this bit) I get: powershell -executionpolicy bypass -File tools/textify.ps1 -Destination wireshark-gtk2 ./COPYING ./NEWS ./README ./README.windows Textified E:\Wireshark\wireshark\COPYING to wireshark-gtk2\COPYING.txt Textified E:\Wireshark\wireshark\NEWS to wireshark-gtk2\NEWS.txt Textified E:\Wireshark\wireshark\README to wireshark-gtk2\README.txt Textified E:\Wireshark\wireshark\README.windows to wireshark-gtk2\README.windows.txt and powershell -executionpolicy bypass -File tools/textify.ps1 -Destination wireshark-gtk2\help help\*.txt Skipping E:\Wireshark\wireshark\help\capture_filters.txt Skipping E:\Wireshark\wireshark\help\capturing.txt Skipping E:\Wireshark\wireshark\help\display_filters.txt Skipping E:\Wireshark\wireshark\help\faq.txt Skipping E:\Wireshark\wireshark\help\getting_started.txt and both the windows buildbots and the petri-dish get the same. The error looks like a problem with line 71 of the script, where all the source files are enumerated. Get-ChildItem returns the leaf node of the supplied path. From the top level source you could just try to run the command line shown, e.g. powershell -executionpolicy bypass -File tools/textify.ps1 -Destination wireshark-gtk2 ./COPYING ./NEWS ./README ./README.windows -- Graham Bloice Gives the same result
L C:\ewireshark2\trunk>powershell -executionpolicy bypass -File tools/textify.ps1 -Destination wireshark-gtk2 ./COPYING ./NEWS ./README ./README.windows Get-ChildItem : A parameter cannot be found that matches parameter name 'File'. At C:\ewireshark2\trunk\tools\textify.ps1:71 char:42 + foreach ($src_file in Get-ChildItem -File <<<< $SourceFiles) { + CategoryInfo : InvalidArgument: (:) [Get-ChildItem], ParameterB indingException + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Comm ands.GetChildItemCommand |
- Follow-Ups:
- Re: [Wireshark-dev] Windows pacaging fails with master
- From: Graham Bloice
- Re: [Wireshark-dev] Windows pacaging fails with master
- References:
- [Wireshark-dev] Windows pacaging fails with master
- From: Anders Broman
- Re: [Wireshark-dev] Windows pacaging fails with master
- From: Graham Bloice
- [Wireshark-dev] Windows pacaging fails with master
- Prev by Date: Re: [Wireshark-dev] Windows pacaging fails with master
- Next by Date: Re: [Wireshark-dev] Windows pacaging fails with master
- Previous by thread: Re: [Wireshark-dev] Windows pacaging fails with master
- Next by thread: Re: [Wireshark-dev] Windows pacaging fails with master
- Index(es):