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\epan.vcxproj]

Regards
Anders

-----Original Message-----
From: wireshark-dev-boun...@wireshark.org 
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Hadriel Kaplan
Sent: den 20 augusti 2015 14:26
To: Developer support list for Wireshark
Subject: [Wireshark-dev] Windows file wildcard support

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 in Windows.

It used to work, using nmake, but the buildbots use cmake and it's not working. 
I thought it was just that setargv.obj wasn't being linked in (as happened in 
bug 10354), but even when I added it in this change it's still not working:

https://code.wireshark.org/review/#/c/10143/

Unfortunately I don't have a Windows platform so I'm just shooting in the dark 
trying to get it to work on the buildbots. (it works fine for
Linux/Mac)

-hadriel
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    https://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:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to