Configure Qt development on Windows + Mac + linux

These build instructions includes support for phonon (mp3 and video playback, etc.) and opensssl (for https support etc.) - because I needed them! And because they are a bit of a pain to set up.

Start with Qt Creator on Mac or linux for the smoothest experience...

Linux

To set up for linux development..

• install Qt and Qt Creator using your favorite distro's package manager
• dump in some sample code and get it compiling and running
• install git using your package manager
• set up a central git repo and push your sample code to it

Mac OS X

To set up for Mac development (I'm using Lion)...

• download Xcode (the primary Apple IDE)
• in Xcode: Preferences --> Downloads With "Components" selected, you will see a list of downloadable components. Look for Command Line Tools, and click on install. You will be prompted for your Apple Developer userid and password. After successfully authenticating, the command line tools component downloads and installs a bunch of goodness, including gcc.
• download the Mac Qt environment, including Qt Creator
• install git and pull down the code
• run Qt Creator and compile and run

Windoze

This gives a Windoze static build of Qt 5.2, yay!

• Get latest OpenSSL source from here, unzip to C:\openssl-1.0.1f.
• Open a VS Developer Prompt and build OpenSSL:

cd C:\openssl-1.0.1f
perl Configure VC-WIN32 no-asm --prefix=C:\openssl-1.0.1f\mdm
ms\do_ms
nmake -f ms\nt.mak
nmake -f ms\nt.mak install
rem And bc setting up paths to openssl is troublesome...
xcopy /S C:\openssl-1.0.1f\mdm\include\openssl\* C:\Qt\qt5-from-tdm\qtbase\include\openssl\
xcopy /S C:\openssl-1.0.1f\mdm\lib\* C:\Qt\qt5-from-tdm\qtbase\lib\
xcopy /S C:\openssl-1.0.1f\mdm\bin\* C:\Qt\qt5-from-tdm\qtbase\bin\

• Get the latest Qt source (I'm using gitorious on tdm, then pulled locally).
• Patch the VS 2013 mkspec to make it build static:

notepad C:\Qt\qt5-from-tdm\qtbase\mkspecs\win32-msvc2013\qmake.conf
# MDM was haere
#QMAKE_CFLAGS_RELEASE    = -O2 -MD
#QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -O2 -MD -Zi
#QMAKE_CFLAGS_DEBUG      = -Zi -MDd
QMAKE_CFLAGS_RELEASE    = -O2 -MT
QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -O2 -MT -Zi
QMAKE_CFLAGS_DEBUG      = -Zi -MTd

• Compile Qt statically in a VS Developer Prompt:

cd C:\Qt\qt-everywhere-opensource-src-5.2.0
set QMAKESPEC=win32-msvc2013
set PATH=%CD%\bin;%PATH%
set PATH=%CD%\qtbase\bin;%PATH%
set PATH=%CD%\qtrepotools\bin;%PATH%
set PATH=%CD%\gnuwin32\bin;%PATH%
set QTDIR=%CD%\qtbase
set QT_QPA_PLATFORM_PLUGIN_PATH=%CD%\qtbase\plugins\platforms

rem configure says "To reconfigure, run nmake confclean and configure."
rem but it seems it is [nmake clean]

rem NOTE use this for 64-bit: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Lib\x64

configure -opengl desktop -confirm-license -qmake -opensource OPENSSL_LIBS="-llibeay32 -lssleay32 -lgdi32" -debug-and-release -platform win32-msvc2013 -static -no-crt -nomake examples -openssl-linked -I C:\openssl-1.0.1f\mdm\include -L C:\openssl-1.0.1f\mdm\lib -L "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Lib" >configure_output.txt
# nmake or jom will do, jom is faster
jom >jom_output.txt

• Create a new "kit" with the newly built Qt!

Regenerating Visual Studio solution on project changes:

• This must be done when the project changes (files added etc)
• Run Visual Studio, but CLOSE THE CURRENT SOLUTION FIRST
• select [Qt->Open Qt Project File...]
• open the same project from the same location
  • it will ask you if you want to regenerate, say yes
  • it will ask a couple more times if you want to overwrite
    • [OK] to saving current changes
    • [Discard] changes and overwrite with new ones from file