[Interest] Process for building Qt on windows 64bit

[Scott Aron Bloom]

Thanks.. I use a similar setup..  Except they are all 32 bit differences...

When I was consulting, it wasn't uncommon to have clients on different versions of Qt...

So far, I got my openssl built for shared lib under 64 bit.. :)  Qt debug is building now..

Scott

From: Alex Malyushytskyy [mailto:alexmalvtk at gmail.com]
Sent: Tuesday, September 24, 2013 5:53 PM
To: Scott Aron Bloom
Cc: Michael Jackson; qt-interest (interest at qt-project.org)
Subject: Re: [Interest] Process for building Qt on windows 64bit

>> Hopefully it will work as easy as you say... Then there are about 5-6 OTHER third party libraries I have to deal with :(
It does work as easy as it was claimed.
Environment set affects which compiler is executed.

Since I am mostly developing on the Windows I have such setup since Qt 3.

Multiple builds of QT in different folders.
I am using  VS addon to manage which Qt version is used.
Depending on VS and Addon version you might have to  specify Qt location once per build or every time you switch configuration.
If you work
I am usually trying to keep all my dependencies in locations  which has platform and builde name as a part of location..
So  having multiple dependencies ( vtk for example ) built in

d:\alex\my documents\Visual Studio 2010\Projects\VTK\vtk-5.8.0.Downloads\vtk-5.8.0.win32\
d:\alex\my documents\Visual Studio 2010\Projects\VTK\vtk-5.8.0.Downloads\vtk-5.8.0.x64\

and defining macros:

   <VTK>d:\alex\my documents\Visual Studio 2010\Projects\VTK\vtk-5.8.0.Downloads\vtk-5.8.0.$(PlatformName)</VTK>
    <VTK_BIN>d:\alex\my documents\Visual Studio 2010\Projects\VTK\vtk-5.8.0.VS2010.$(PlatformName)</VTK_BIN>
allows me  easy to refer to appropriate location in VC project:

$(VTK_BIN)\bin\$(ConfigurationName);

As a result I can switch between builds and platform from the same VS instance.

Alex


On Tue, Sep 24, 2013 at 4:31 PM, Scott Aron Bloom <scott.bloom at onshorecs.com<mailto:scott.bloom at onshorecs.com>> wrote:
Thanks!!  Hopefully it will work as easy as you say... Then there are about 5-6 OTHER third party libraries I have to deal with :(

Scott

-----Original Message-----
From: Michael Jackson [mailto:imikejackson at gmail.com<mailto:imikejackson at gmail.com>]
Sent: Tuesday, September 24, 2013 4:32 PM
To: Scott Aron Bloom
Subject: Re: [Interest] Process for building Qt on windows 64bit

Do the same thing but from a "Visual Studio x64 Command Prompt" instead. This will yield a 64 bit build.

MAKE SURE YOU ARE RUNNING AT LEAST THE FIRST SERVICE PACK OF WHAT EVER VISUAL STUDIO. There are known 64 bit compiler bugs in all the initial Visual Studio releases that are solved with the Service Pack updates.

Hope that helps.
Mike Jackson

On Sep 24, 2013, at 7:04 PM, Scott Aron Bloom <Scott.Bloom at onshorecs.com<mailto:Scott.Bloom at onshorecs.com>> wrote:

> Im on qt 4.8.4 (cant move to 5.x at the company yet) and I a request from a customer for a 64 bit windows release.
>
> The first step, will be building Qt under 64 bit.
>
> Does anyone have a "this is what I do" sheet?
>
> My 32bit flow, is simple, unzip, run configure, build it inside visual
> studio using the following switches -debug-and-release -opensource
> -shared -stl -platform
> win32-msvc2008
> -vcproj
> -qt-libpng
> -qt-zlib
> -qt-libjpeg
> -qt-zlib
> -openssl -I c:/Qt/openssl-0.9.8o/inc32 -L
> c:/Qt/openssl-0.9.8o/out32dll -no-qt3support -nomake demos -nomake
> examples -no-phonon -no-phonon-backend -qt-sql-sqlite -qt-sql-odbc
>
> And walla...
>
> Is it simply a matter of changing what Visual Studio path is set?
>
> Any help would be appreciated.
>
> Scott
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org<mailto:Interest at qt-project.org>
> http://lists.qt-project.org/mailman/listinfo/interest

_______________________________________________
Interest mailing list
Interest at qt-project.org<mailto:Interest at qt-project.org>
http://lists.qt-project.org/mailman/listinfo/interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20130925/1ef724e5/attachment.html>