Wireshark-dev: Re: [Wireshark-dev] Trunk Windows CMake builds are broken
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Thu, 21 Aug 2014 02:04:09 -0700
On Aug 21, 2014, at 1:57 AM, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:

> This obviously worked before the merge of ExtCap, so that has disturbed things.  The CMake build should be using the generated one in the CMake build directory, i.e. C:\buildbot\wireshark\wireshark-master-64\win7x64\build\cmbuild\config.h, but the nmake build copy is getting in the mix.

I don't think that building using build system A and then, without first cleaning up all the generated files from build system A, building using build system B is guaranteed to work.  (I've had problems with, for example, an in-tree autotools build followed by an out-of-tree CMake build - *before* the extcap stuff was checked in, so it wasn't extcap's fault.)

We should either do a separate checkout for the Windows CMake build or should do an "nmake -f Makefile.nmake maintainer-clean" before the CMake build.