Wireshark-dev: Re: [Wireshark-dev] Problems with Windows build environment
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Tue, 24 Sep 2013 19:01:33 +0200
On Tue, Sep 24, 2013 at 04:52:40PM +0100, Graham Bloice wrote:
> This advice is correct for the current build system using nmake, since the
> builds are done in-source, i.e. the object files and libraries a generated
> inside the source tree.  Switch from x86 to amd64 and vice-versa does
> require a distclean.
> 
> However, Joerg is experimenting with a CMake build which I assume is being
> done out-of-tree, i.e. a separate build directory for each of x86 and amd64.

Yes, I'm using a separate build directory and currently I delete the complete
content before running cmake

C:\wireshark>dir
...
23.09.2013  17:43    <DIR>          .
23.09.2013  17:43    <DIR>          ..
24.09.2013  16:24    <DIR>          build
23.09.2013  17:43             1.373 setup.bat
24.07.2013  02:44               938 setup.bat~
24.09.2013  17:05    <DIR>          trunk
23.09.2013  11:21    <DIR>          Wireshark-win32-libs
23.09.2013  11:28    <DIR>          Wireshark-win64-libs

Where build is the build directory and trunk is the svn source.

Ciao
    Jörg

PS: The hint with copying mspdbsrv.exe didn't work - but I didn't expect it
    to. Undone since.
-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.