[Wireshark-dev] Windows automated builds migrated to CMake

We reached a bit of a milestone today. The packages created by the 32-bit and 64-bit Windows builders at https://buildbot.wireshark.org/trunk/waterfall are now produced using CMake and MSBuild. Thanks to everyone for helping to get the Windows CMake environment up and running!

Re: [Wireshark-dev] Windows automated builds migrated to CMake

Woohoo. Change to delete *.nmake incoming :-) On 16 April 2015 at 04:06, Gerald Combs wrote: > We reached a bit of a milestone today. The packages created by the > 32-bit and 64-bit Windows builders at > https://buildbot.wireshark.org/trunk/waterfall are now produced using > CMake and MSBuild.

Re: [Wireshark-dev] Windows automated builds migrated to CMake

Hi Am I correct, that as for now, there is no plan to move the download of the necessary libraries for building Wireshark on Windows from the nmake system to cmake as well? Also, the wiki pages do not seem to reflect the cmake build and the buildbot waterfall display only seem to run cmake, but n

Re: [Wireshark-dev] Windows automated builds migrated to CMake

Awesome. Good job! - Juanjo On Thursday, April 16, 2015, Graham Bloice wrote: > Woohoo. > > Change to delete *.nmake incoming :-) > > On 16 April 2015 at 04:06, Gerald Combs > wrote: > >> We reached a bit of a milestone today. The packages created by the >> 32-bit and 64-bit Windows builders a

Re: [Wireshark-dev] Windows automated builds migrated to CMake

On 16 April 2015 at 09:29, Roland Knall wrote: > Hi > > Am I correct, that as for now, there is no plan to move the download of > the necessary libraries for building Wireshark on Windows from the nmake > system to cmake as well? > > The download of libraries is in CMake (excepting QT). See chan

Re: [Wireshark-dev] Windows automated builds migrated to CMake

On 16 April 2015 at 09:29, Roland Knall wrote: > Also, the wiki pages do not seem to reflect the cmake build and the > buildbot waterfall display only seem to run cmake, but not build using it? > Would be helpful to setup a cmake enforced build on Windows, which is still > a little bit tricky (ev

Re: [Wireshark-dev] Windows automated builds migrated to CMake

Hi Very cool + 1 The waterfall display was a little bit misleading, but found it now. Still waiting for the get-go in my company to install VS2013, but will try it as soon as possible. As of dependencies, this leaves more or less the mac plattform with the setup script. I played around with that

Re: [Wireshark-dev] Windows automated builds migrated to CMake

On 16 April 2015 at 10:11, Roland Knall wrote: > Hi > > Very cool + 1 > > The waterfall display was a little bit misleading, but found it now. Still > waiting for the get-go in my company to install VS2013, but will try it as > soon as possible. > VS2015 is out soon! I suspect that the 1.99.x a

Re: [Wireshark-dev] Windows automated builds migrated to CMake

Great! Good job! Cheers, Balint 2015-04-16 10:19 GMT+02:00 Graham Bloice : > Woohoo. > > Change to delete *.nmake incoming :-) > > On 16 April 2015 at 04:06, Gerald Combs wrote: >> >> We reached a bit of a milestone today. The packages created by the >> 32-bit and 64-bit Windows builders at >> h

Re: [Wireshark-dev] Windows automated builds migrated to CMake

2015-04-16 5:06 GMT+02:00 Gerald Combs : > We reached a bit of a milestone today. The packages created by the > 32-bit and 64-bit Windows builders at > https://buildbot.wireshark.org/trunk/waterfall are now produced using > CMake and MSBuild. > > Thanks to everyone for helping to get the Windows C

Re: [Wireshark-dev] Windows automated builds migrated to CMake

On 16 April 2015 at 11:49, Pascal Quantin wrote: > > > 2015-04-16 5:06 GMT+02:00 Gerald Combs : > >> We reached a bit of a milestone today. The packages created by the >> 32-bit and 64-bit Windows builders at >> https://buildbot.wireshark.org/trunk/waterfall are now produced using >> CMake and MS

Re: [Wireshark-dev] Windows automated builds migrated to CMake

2015-04-16 14:55 GMT+02:00 Graham Bloice : > > > On 16 April 2015 at 11:49, Pascal Quantin > wrote: > >> >> >> 2015-04-16 5:06 GMT+02:00 Gerald Combs : >> >>> We reached a bit of a milestone today. The packages created by the >>> 32-bit and 64-bit Windows builders at >>> https://buildbot.wireshar

Re: [Wireshark-dev] Windows automated builds migrated to CMake

Hi, The checkAPI target is missing from the cmake build isn't it? Regards Anders Pascal Quantin skrev den 2015-04-16 15:09: 2015-04-16 14:55 GMT+02:00 Graham Bloice >: On 16 April 2015 at 11:49, Pascal Quantin mailto:pascal.quan...@gmail.com>> wrot

Re: [Wireshark-dev] Windows automated builds migrated to CMake

It's defined in cmake/modules/UseCheckAPI.cmake which is included by the top-level CMakeLists.txt. It's run by the Visual Studio Code Analysis builder. On 4/16/15 7:12 AM, Anders Broman wrote: > > Hi, > The checkAPI target is missing from the cmake build isn't it? > Regards > Anders > > Pascal Qua

Re: [Wireshark-dev] Windows automated builds migrated to CMake

We're also missing a .dmg target (packaging/macosx/osx-dmg.sh). I think that's the only thing missing on the OS X builders. On 4/16/15 2:11 AM, Roland Knall wrote: > Hi > > Very cool + 1 > > The waterfall display was a little bit misleading, but found it now. > Still waiting for the get-go in my c

Re: [Wireshark-dev] Windows automated builds migrated to CMake

On 4/16/15 5:55 AM, Graham Bloice wrote: > > This is down to the subsystem type. The nmake builds are marked as > "Windows Gui" and the CMake builds as "Windows Console". It's a linker > flag, supplied in $(guiflags) for nmake builds (or $(conflags) for command > line programs e.g. tshark.exe).