Wireshark-dev: Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: João Valverde <joao.valverde@xxxxxxxxxxxxxxxxxx>
Date: Wed, 30 Mar 2016 03:10:04 +0100


On 29-03-2016 21:46, Roland Knall wrote:

Sorry, late over here. You could try with cmake 3.5rc2. But beside that,
I did not get WS compile correctly with VS2013 for some time now, need
to use VS2015 myself.
Just another data point, I tried building on Windows 10 x64 with VS2015 and the latest of everything I could find (cmake, etc), just following along the dev guide, it worked really well, no problems at all. 




On Tue, Mar 29, 2016 at 10:04 PM, Michael Mann <mmann78@xxxxxxxxxxxx
<mailto:mmann78@xxxxxxxxxxxx>> wrote:

    It didn't generate one (otherwise I would have attached it).  When
    it does, the output (like that below) would include a note about
    "See also CMakeError.log)" at the last line (right after line about
    CMakeOutput.log)
    -----Original Message-----
    From: Roland Knall <rknall@xxxxxxxxx <mailto:rknall@xxxxxxxxx>>
    To: Developer support list for Wireshark
    <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>
    Sent: Tue, Mar 29, 2016 3:48 pm
    Subject: Re: [Wireshark-dev] Building with CMake on Win10 and VS2013
    (win64)

    Take a look in your build directory, there must be a folder called
    CMakeFiles. In it, you'll find CMakeError.log. This file should
    contain, at it's bottom, the call which lead to the error and a more
    detailed error information in regard to the missing utility.

    regards
    Roland

    On Tue, Mar 29, 2016 at 9:14 PM, Michael Mann <mmann78@xxxxxxxxxxxx
    <mailto:mmann78@xxxxxxxxxxxx>> wrote:

        I had gotten CMake to build on my setup a few months back, but
        it was a bit "quirky" (I had to keep deleting and regenerating
        the build directory because consecutive rebuilds would fail).
        I tried again with a more recent version of master (maybe a week
        old at this point) and can't seem to get the setup to complete
        (following
        https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html) .
        Attached is the log file generated, with terminal output below.
        It feels like I'm just missing a simple build option in my
        setup, something to determine 64 vs 32 bit (or X86 vs X64),
        because I would think configuration would be smart enough to
        determine the endianness of Windows.
        Vitals: Windows 10, VS2013 (Community Edition), trying to build
        64-bit Wireshark.
        c:\wireshark>mysetup.bat
        c:\wireshark>set CYGWIN=nodosfilewarning
        c:\wireshark>set WIRESHARK_BASE_DIR=C:\wireshark
        c:\wireshark>set WIRESHARK_TARGET_PLATFORM=win64
        c:\wireshark>set QT5_BASE_DIR=C:\Qt\5.5\msvc2013_64
        c:\wireshark>set PLATFORM=x64
        c:\wireshark>mkdir wsbuild64
        c:\wireshark>cd wsbuild64
        c:\wireshark\wsbuild64>..\mygenbuild.bat
        c:\wireshark\wsbuild64>cmake