Hi Martin,

2016-11-06 12:25 GMT+01:00 Martin Mathieson <
[email protected]>:

> Hi,
>
> I've spent quite a while trying to get a Windows build going with
> trunk, following the instructions at
> https://www.wireshark.org/docs/wsdg_html/#ChSetupWin32
>
> My first problem was trying to build the Win64/x64 build against
> Microsoft Visual Studio 2013 Community Edition.  If it doesn't support
> 64-bit builds, we should probably make this clearer.
>

It does support 64 bits (I'm using it daily). You should have a 'VS2013 x64
Cross Tools Command Prompt' shortcut createdin C:\Program Files
(x86)\Microsoft Visual Studio 12.0\Common7\Tools\Shortcuts folder and that
launches C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\vcvarsall.ba3 with  x86_amd64 option.


> Next, the link for Qt download
> (https://www.qt.io/download-open-source/) leads to the 'unified x86'
> installer, which as far as I could see only installed the 64-bit
> edition?
>
> After I saw a 32-bit vs 64-bit link error, I instead found the 5.6
> Windows 32-bit qt installer on
> http://download.qt.io/archive/qt/5.6/5.6.1-1/.  However, after
> installing qt-opensource-windows-x86-msvc2013-5.6.1-1.exe from here
> and setting my environment like this...
>
> set CYGWIN=nodosfilewarning
> set WIRESHARK_BASE_DIR=C:\Development
> set WIRESHARK_TARGET_PLATFORM=win32
> set QT5_BASE_DIR=C:\Qt\5.6.1\5.6\msvc2013
> set WIRESHARK_VERSION_EXTRA=-MartinDesktop
> set WIRESHARK_CYGWIN_INSTALL_PATH=C:\cygwin64
> set VisualStudioVersion=12.0
>
> ... cmake doesn't find any of the Qt5 packages.  I was able to build
> the other wireshark project targets at this point.
>

I'm using the 5.6.2 installers
http://download.qt.io/official_releases/qt/5.6/5.6.2/qt-opensource-windows-x86-msvc2013_64-5.6.2.exe
and
http://download.qt.io/official_releases/qt/5.6/5.6.2/qt-opensource-windows-x86-msvc2013-5.6.2.exe
respextively for 64 bits and 32 bits . My environment variables are:
set QT5_BASE_DIR=C:\Qt\x64\5.6\msvc2013_64
set WIRESHARK_TARGET_PLATFORM=win64
set WIRESHARK_LIB_DIR=c:\Wireshark-win64-libs
for 64 bits
and
set QT5_BASE_DIR=C:\Qt\x86\5.6\msvc2013
set WIRESHARK_TARGET_PLATFORM=win32
set WIRESHARK_LIB_DIR=c:\Wireshark-win32-libs
for 32 bits.

My CMake version is 3.6.2 in case it matters.
Did you clean your CMake cache before configuring the environment variable
(in case you gave a try before configuring QT5_BASE_DIR)?


> CMakeCache.txt shows that it didn't find the cmake files for Qt5 at all..
>
> //The directory containing a CMake configuration file for Qt5Core.
> Qt5Core_DIR:PATH=Qt5Core_DIR-NOTFOUND
>
> //The directory containing a CMake configuration file for Qt5LinguistTools.
> Qt5LinguistTools_DIR:PATH=Qt5LinguistTools_DIR-NOTFOUND
>
> //The directory containing a CMake configuration file for Qt5Multimedia.
> Qt5Multimedia_DIR:PATH=Qt5Multimedia_DIR-NOTFOUND
>
> //The directory containing a CMake configuration file for Qt5PrintSupport.
> Qt5PrintSupport_DIR:PATH=Qt5PrintSupport_DIR-NOTFOUND
>
> //The directory containing a CMake configuration file for Qt5Svg.
> Qt5Svg_DIR:PATH=Qt5Svg_DIR-NOTFOUND
>
> //The directory containing a CMake configuration file for Qt5Widgets.
> Qt5Widgets_DIR:PATH=Qt5Widgets_DIR-NOTFOUND
>
> //The directory containing a CMake configuration file for Qt5WinExtras.
> Qt5WinExtras_DIR:PATH=Qt5WinExtras_DIR-NOTFOUND
>
> Any ideas what I might have done wrong, and where the CMake files for
> Qt5 should be?
>
> Best regards,
> Martin
> ____________________________________________________________
> _______________
> Sent via:    Wireshark-dev mailing list <[email protected]>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:[email protected]?subject=
> unsubscribe
>
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to