Re: [Wireshark-dev] Windows file wildcard support

2015-08-20 Thread Hadriel Kaplan
Ahh, yeah that would be a problem. Thanks! -hadriel On Thu, Aug 20, 2015 at 8:38 AM, Anders Broman wrote: > Hi, > I don't build with CMAKE currently so I can't test but it might still be a > problem with setargv > We get this warning on the buildboot: >> LINK : warning LNK4044: unrecognized opti

Re: [Wireshark-dev] Windows file wildcard support

2015-08-20 Thread Pascal Quantin
2015-08-20 14:38 GMT+02:00 Anders Broman : > Hi, > I don't build with CMAKE currently so I can't test but it might still be a > problem with setargv > We get this warning on the buildboot: > > LINK : warning LNK4044: unrecognized option '/RELEASE;setargv.obj'; > ignored > [C:\buildbot\wireshark\wi

Re: [Wireshark-dev] Windows file wildcard support

2015-08-20 Thread Anders Broman
Hi, I don't build with CMAKE currently so I can't test but it might still be a problem with setargv We get this warning on the buildboot: > LINK : warning LNK4044: unrecognized option '/RELEASE;setargv.obj'; ignored > [C:\buildbot\wireshark\wireshark-master-32\windows-8.1-x86\build\cmbuild\epan\e

[Wireshark-dev] Windows file wildcard support

2015-08-20 Thread Hadriel Kaplan
Howdy, Can someone with a Windows build platform try building the current repo and run the mergecap test suite and figure out how to get the file wildcarding to work? The Windows buildbots are failing due to the test suite failing, and it's failing because the wildcard method doesn't seem to work i

[Wireshark-dev] WIRESHARK_QUIT_AFTER_CAPTURE

2015-08-20 Thread Dario Lombardo
Hi list Wireshark can quit after capture when the variable WIRESHARK_QUIT_AFTER_CAPTURE is set and -a and -k are activated. This is used mainly for testing purposes, according to the manual. This feature doesn't work in offline mode, when opening a local file. This would be very useful, so I tried