Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Building Qt 5.2.1 in latest Visual Studios
Forum Updated to NodeBB v4.3 + New Features

Building Qt 5.2.1 in latest Visual Studios

Scheduled Pinned Locked Moved Installation and Deployment
39 Posts 4 Posters 12.7k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • sierdzioS Offline
    sierdzioS Offline
    sierdzio
    Moderators
    wrote on last edited by
    #16

    Here is a list of all modules: "link":http://qt-project.org/doc/qt-5/qtmodules.html.

    Seems like you are using wrong mkspecs. Are you running that from your MSVC-enabled command line? To make the compiler choice specific, add this to configure:
    @
    -platform win32-msvc2013
    @

    (or msvc2012, depending on your choice). If you really, really just need QtCore, it will probably take some iterations to nail a working configure line, as it is a highly specific use case (most people compile whole Qt, some skip webkit and QtQuick1, but almost nobody goes further :P).

    I'll give you 2 ways to do it, but there are many more.

    remove all folders from your Qt dir, except for qtbase, qttools and qtdoc, then run configure as usual. This will still not be ideal for you: modules like QtNetwork are inside qtbase (but it is a small module, compiles in seconds)

    keep patiently removing all Qt modules with -skip flag...

    (Z(:^

    1 Reply Last reply
    0
    • sierdzioS Offline
      sierdzioS Offline
      sierdzio
      Moderators
      wrote on last edited by
      #17

      OK, I'll throw in the third way: run the configure line as usual, but then don't run the global Makefile. Instead, cd into qtbase and run nmake (or jom) there. This should only build QtCore, QtNetwork, and other base modules.

      (Z(:^

      1 Reply Last reply
      0
      • M Offline
        M Offline
        mwpowellhtx
        wrote on last edited by
        #18

        As long as I can identify them (more or less), yes. Thanks for the tips (and the patience!)...

        1 Reply Last reply
        0
        • M Offline
          M Offline
          mwpowellhtx
          wrote on last edited by
          #19

          I added -platform win32-mscv2012, and same error. Yes, I need an MSVC command line?

          1 Reply Last reply
          0
          • M Offline
            M Offline
            mwpowellhtx
            wrote on last edited by
            #20

            I'm just reading the notes: http://qt-project.org/wiki/Building_Qt_5_from_Git

            And nowhere after configure does it say to CD qtbase when using jom, or any of the other options. Or maybe I am reading it wrong?

            Oh! Bit of a clue: the prefix is where the stuff lands, so that's why...

            I am spoiled by IDEs, workspace and project files, which are a dialect all their own...

            1 Reply Last reply
            0
            • sierdzioS Offline
              sierdzioS Offline
              sierdzio
              Moderators
              wrote on last edited by
              #21

              Qt is being built based on Makefiles (which are being normally read and executed by make on Unix and nmake on Windows). When you run "configure", it will do the following for you:

              • bootstrap Qt tools (namely: create qmake binary, which is then used to generate Makefiles, create moc and friends)
              • generate main Makefile
              • generate a separate Makefile for every module

              So. Standard Qt compilation instructions (the ones you have inked) instruct you to just run "nmake". This will run the main Makefile, which in turn runs all module Makefiles.

              But you are not forced to do it: if you simply cd into any module and run nmake there, only that single module will be compiled.

              All resulting libraries and binaries are always put into qtbase.

              Having said all this, I still think that if you are a "mid-range" end user, you should not be concerned about all this: just grab the precompiled Qt installer, or compile the whole package without getting into advanced and custom configuration. You will probably waste much more time trying to compile Qt in your specific way (we are already talking for the whole day), especially on Windows where things tend to break every time Microsoft decides to bless us all with an update to their compiler.

              Now, getting to that error. It seems to be coming from precompiled headers. I don't remember the dev consensus exactly, but it might be that headers are precompiled in the .zip package. I am no expert here, but they may not be compatible with MSVC 2k13 (MS has a habit of breaking the compatibility on a regular basis). In that case, you may have more luck checking out from git (but that will take a long time + pull the Perl dependency).

              (Z(:^

              1 Reply Last reply
              0
              • M Offline
                M Offline
                mwpowellhtx
                wrote on last edited by
                #22

                Ah, I didn't need to change dir to qtbase, there is no Makefile there. Actually it's in the <path/to/qt5>.

                1 Reply Last reply
                0
                • M Offline
                  M Offline
                  mwpowellhtx
                  wrote on last edited by
                  #23

                  Configure done. Now jom is running. Coffee, movie...

                  1 Reply Last reply
                  0
                  • M Offline
                    M Offline
                    mwpowellhtx
                    wrote on last edited by
                    #24

                    I'd agree with the installer approach if I was the only end-user. We're supporting software across platforms, so need the flexibility to build it how we want across platforms.

                    I'm not sure how long the build runs (2 cores, 1 hour?), or if JOM is actually helping at all. At least it's building. We'll see...

                    1 Reply Last reply
                    0
                    • M Offline
                      M Offline
                      mwpowellhtx
                      wrote on last edited by
                      #25

                      Actually, the build was finishing just as I wrote that...

                      1 Reply Last reply
                      0
                      • M Offline
                        M Offline
                        mwpowellhtx
                        wrote on last edited by
                        #26

                        So... ~50 minutes, give or take. JOM helped a little? More cores, maybe a non factor. Not sure if I set the CL to /MP, now that I think about it. I'm sure it could be helped.

                        1 Reply Last reply
                        0
                        • M Offline
                          M Offline
                          mwpowellhtx
                          wrote on last edited by
                          #27

                          Okay, now what? I've got some includes to include, and some cmakes in CD to make?

                          Actually I see a bunch of promising output in qtbase/lib to go with the includes.

                          1 Reply Last reply
                          0
                          • M Offline
                            M Offline
                            mwpowellhtx
                            wrote on last edited by
                            #28

                            ... So really we "just" need the includes and the output from the prefix PWD/qtbase? The harder part is establishing a strategy for maintenance, end-user consumption, etc.

                            1 Reply Last reply
                            0
                            • M Offline
                              M Offline
                              mwpowellhtx
                              wrote on last edited by
                              #29

                              Okay, I reconfigured, no prefix, "qtbase/lib" dropped "in place" alongside "qtbase/include". I set the CL environment variable and ran JOM; and the build that took nearly 1 hour before, took maybe 2 minutes (conservatively)! That's on an 8-core machine. I can hardly believe that. It sure does look like the DLLs and all are there. WOW,

                              1 Reply Last reply
                              0
                              • M Offline
                                M Offline
                                mwpowellhtx
                                wrote on last edited by
                                #30

                                If I could mark it as an answer I would. Thanks again for setting me straight.

                                1 Reply Last reply
                                0
                                • sierdzioS Offline
                                  sierdzioS Offline
                                  sierdzio
                                  Moderators
                                  wrote on last edited by
                                  #31

                                  Well, you don't need to build Qt for your end-users. For them, you just deploy the libraries you need ("link":http://qt-project.org/doc/qt-5/windows-deployment.html, there are guides like that for every platform). But of course, you know your situation better than I do.

                                  [quote]Okay, now what? I’ve got some includes to include, and some cmakes in CD to make?[/quote]

                                  That depends on what you want to achieve. If you want to use Qt Creator for development, then you just need to point it to your newly built qmake.exe, and it will configure itself automatically; no need to link or include anything by hand.

                                  If you want to use Visual Studio - there is a plugin for that available on the downloads page.

                                  If you want to run everything from command line, you need to add qtbase/bin to PATH.

                                  [quote]So really we “just” need the includes and the output from the prefix PWD/qtbase?[/quote]

                                  qtbase/bin, qtbase/includes, qtbase/mkspecs. You can automatically separate those if you perform an out of source build, like this:
                                  @
                                  // assuming Qt source code is in qt-src
                                  mkdir qt-build
                                  cd qt-build
                                  ..\qt-src\configure <your Qt flags> -prefix CD\qtbase
                                  nmake
                                  nmake install
                                  @

                                  This will compile and install Qt to qt-build, leaving your Qt source code intact.

                                  (Z(:^

                                  1 Reply Last reply
                                  0
                                  • M Offline
                                    M Offline
                                    mwpowellhtx
                                    wrote on last edited by
                                    #32

                                    Right I understand re: developers and deployed binaries. The configure make system is a little foreign to me is all, and when I have used it a bit opaque if cumbersome. I'm sure not once you get used to it.

                                    Anyhow, I expect there's some way to identify libs (and dlls or .sos) for linkage on the other side of their includes. Much of which is IDE specific.

                                    The much harder part about our situation is mitigating cross platform risk factors, less technical and more geo-political in nature, coordinating the builds.

                                    Thanks...

                                    1 Reply Last reply
                                    0
                                    • sierdzioS Offline
                                      sierdzioS Offline
                                      sierdzio
                                      Moderators
                                      wrote on last edited by
                                      #33

                                      Yeah, cross-platform build servers are always problematic. Qt makes the compilation part quite easy (the same code works on all platforms without any changes), but there always are lots of other problems to solve ;)

                                      OK, I hope I've helped you at least a bit. If there are more questions, please ask. Have fun! :)

                                      (Z(:^

                                      1 Reply Last reply
                                      0
                                      • R Offline
                                        R Offline
                                        robinrowe
                                        wrote on last edited by
                                        #34

                                        I can build QT using VC++ 2013 without OpenSSL, but with OpenSSL I get the errors below.

                                        Suggestions?

                                        Robin

                                            cl -c -FIqt_pch.h -Yuqt_pch.h -Fp.pch\debug\Qt5Networkd_pch.pch -nologo
                                        

                                        -Zm200 -Zc:wchar_t -Zi -MDd -GR -W3 -w34100 -w34189 /Fd....\lib\Qt5Networkd.pdb
                                        -DUNICODE -DWIN32 -DQT_NO_USING_NAMESPACE -DQT_BUILD_NETWORK_LIB -DQT_BUILDING_
                                        QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRI
                                        NGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x040800 -D_US
                                        E_MATH_DEFINES -DQT_NO_EXCEPTIONS -DQT_CORE_LIB -I"C:\qt\openssl-1.0.1f\openssl-
                                        1.0.1f\include" -I"....\include" -I"....\include\QtNetwork" -I"....\include\Q
                                        tNetwork\5.2.1" -I"....\include\QtNetwork\5.2.1\QtNetwork" -I"tmp" -I"..\3rdpar
                                        ty\zlib" -I"kernel" -I"....\include\QtCore\5.2.1" -I"....\include\QtCore\5.2.1
                                        \QtCore" -I"....\include\QtCore" -I".moc\debug" -I"....\mkspecs\win32-msvc2010
                                        " -Fo.obj\debug\ @C:\Users\rower\AppData\Local\Temp\nm68AA.tmp
                                        qhttpnetworkreply.cpp
                                        C:\qt\openssl-1.0.1f\openssl-1.0.1f\include\openssl/ssl.h(1) : error C2059: synt
                                        ax error : '.'
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(69) : error C2143: syntax error : missing ';' before ''
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(69) : error C4430: missing type specifier - int assumed. Note: C++ d
                                        oes not support default-int
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(69) : warning C4183: 'createSsl': missing return type; assumed to be
                                        a member function returning 'int'
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(70) : error C2061: syntax error : identifier 'SSL'
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(79) : error C2143: syntax error : missing ';' before '
                                        '
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(79) : error C4430: missing type specifier - int assumed. Note: C++ d
                                        oes not support default-int
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(80) : error C2143: syntax error : missing ';' before ''
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(80) : error C4430: missing type specifier - int assumed. Note: C++ d
                                        oes not support default-int
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(81) : error C2143: syntax error : missing ';' before '
                                        '
                                        c:\qt\qt-everywhere-opensource-src-5.2.1\qt-everywhere-opensource-src-5.2.1\qtba
                                        se\include\qtnetwork\5.2.1\qtnetwork\private../../../../../src/network/ssl/qssl
                                        context_p.h(81) : error C4430: missing type specifier - int assumed. Note: C++ d
                                        oes not support default-int

                                        1 Reply Last reply
                                        0
                                        • M Offline
                                          M Offline
                                          mwpowellhtx
                                          wrote on last edited by
                                          #35

                                          Research C4430? Possibly a language standard thing? I don't know the configure option(s), but could C++11 (or other) be specified?

                                          1 Reply Last reply
                                          0

                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Users
                                          • Groups
                                          • Search
                                          • Get Qt Extensions
                                          • Unsolved