Wireshark · Wireshark-dev: Re: [Wireshark-dev] Qt version for the Wireshark Windows build

[Roland Knall <rknall@xxxxxxxxx>]

That's exactly the thing. The Onlineinstaller for 5.3.1 is not working ('cause they turned of the URLs), and the 64bit installer only installed the msvc2013 directory.

On Wed, Jun 3, 2015 at 8:03 PM, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:

What does running "find /cygdrive/c/Qt -iname qt5core.dll -exec file {} +" under Cygwin show on your system? I get the following:

/cygdrive/c/Qt/5.3/msvc2013_64_opengl/bin/Qt5Core.dll: PE32+ executable (DLL) (GUI) x86-64, for MS Windows
/cygdrive/c/Qt/5.3/msvc2013_opengl/bin/Qt5Core.dll:    PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
/cygdrive/c/Qt/Tools/QtCreator/bin/Qt5Core.dll:        PE32 executable (DLL) (GUI) Intel 80386, for MS Windows

I originally installed the Qt 5.3 MSVC 2013 32-bit and 64-bit OpenGL packages using the online installer and recently upgraded using the maintenance tool.

On 6/3/15 10:38 AM, Roland Knall wrote:
> Hi
>
> That was indeed the version I used. The issue is, although the exe's say
> 64bit on the outside, they actually install a 64bit QtCreator, but a 32bit
> library version. What I need would be the 64bit version. The reason seems
> to be, to force the open-source version of Qt to always use the latest
> version of Qt. Which I can understand, but in this case it really annoys me
> quite a bit.
>
> I guess, I have no other choice to compile the while thing again.
>
> regards,
> Roland
>
> On Wed, Jun 3, 2015 at 5:50 PM, Graham Bloice <graham.bloice@xxxxxxxxxxxxx
> <mailto:graham.bloice@xxxxxxxxxxxxx>> wrote:
>
>     I did do a quick check when Roland asked, and got there
>     from https://www.qt.io/download-open-source/ -> Qt 5.3 and all older
>     versions of Qt are available in the archive
>     -> http://download.qt.io/archive/qt/ and so on, but wondered if that
>     was the version that he said actually downloaded a 32 bit copy.
>
>
>     On 3 June 2015 at 16:39, Gerald Combs <gerald@xxxxxxxxxxxxx

>     <mailto:gerald@xxxxxxxxxxxxx>> wrote:
>
>         It looks like direct downloads are available at
>
>             https://download.qt.io/official_releases/qt/
>
>         I got there by copying one of the online installer links listed at
>         https://www.qt.io/download-open-source/ and trimming off the file
>         and version.
>
>         On 6/3/15 7:32 AM, Roland Knall wrote:
>         > Hi
>         >
>         > Is it possible to download the Qt version, with which the
>         buildbot builds
>         > the windows version of Wireshark? Our company has switched to 5.4
>         and the
>         > plugin I am building uses a Qt class, which introduced flags only
>         available
>         > with 5.4. If I load my plugin in wireshark, wireshark claims the
>         missing
>         > flags and functions (as it runs with Qt 5.3.1 and of course has
>         never seen
>         > those methods).
>         >
>         > So I would be able to build with 5.3.1, but the issue being, that
>         Digia
>         > does not allow the 64bit version of older releases to be
>         downloaded (if you
>         > do, you end up with the 32bit, although the download clearly
>         states 64bit).
>         >
>         > So, long story short, does anyone have a 5.3.1 version with real
>         64bit
>         > lying around or can I download the buildbot version somewhere?
>         anonsvn did
>         > not contain a version for msvc2013.
>         >
>         > regards,
>         > Roland
>         >
>         > p.s.: I know I can build from scratch. so far I am avoiding that,
>         but it
>         > might be my only option left.
>         >
>         >
>         >
>         ___________________________________________________________________________
>         > Sent via:    Wireshark-dev mailing list

>         <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>
>         > Archives:    https://www.wireshark.org/lists/wireshark-dev
>         > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>         >              mailto:wireshark-dev-request@xxxxxxxxxxxxx
>         <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
>         >
>
>         ___________________________________________________________________________
>         Sent via:    Wireshark-dev mailing list
>         <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>
>         Archives:    https://www.wireshark.org/lists/wireshark-dev
>         Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>                      mailto:wireshark-dev-request@xxxxxxxxxxxxx
>         <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
>
>
>
>
>     --
>     Graham Bloice
>
>     ___________________________________________________________________________
>     Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx
>     <mailto:wireshark-dev@xxxxxxxxxxxxx>>
>     Archives:    https://www.wireshark.org/lists/wireshark-dev
>     Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>                  mailto:wireshark-dev-request@xxxxxxxxxxxxx
>     <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe

>
>
>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe