Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. QT 5.7 MSVC 2015 Static Builds Not Working
Qt 6.11 is out! See what's new in the release blog

QT 5.7 MSVC 2015 Static Builds Not Working

Scheduled Pinned Locked Moved Solved General and Desktop
4 Posts 2 Posters 2.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.
  • C Offline
    C Offline
    Crag_Hack
    wrote on last edited by
    #1

    I'm having trouble using my QT 5.7 MSVC 2015 static builds, both 32-bit and 64-bit. This is the commands I run and the output I get (tested with 32 bit as well):

    C:\Users\Josh>set PATH=C:\Qt\static\Qt 5.7.0 MSVC2015_Static_x64\bin;%PATH%
    
    C:\Users\Josh>cd "\Users\Josh\Mozy Sync\ReplicatorNew\ReplicatorNew"
    
    C:\Users\Josh\Mozy Sync\ReplicatorNew\ReplicatorNew>qmake ReplicatorNew.pro
    Could not find qmake configuration file win32-msvc2015.
    Error processing project file: ReplicatorNew.pro
    

    Configure was run with the following:

    configure -debug-and-release -confirm-license -platform win32-msvc2015 -opengl desktop -static -target xp -nomake examples -no-compile-examples -nomake tests -prefix C:\Qt\static\MSVC2015_Static_x86 -openssl -L C:\OpenSSL-win32\lib -l libeay32 -l ssleay32 -I C:\OpenSSL-win32\include -qt-libpng -qt-libjpeg -qt-zlib
    
    configure -debug-and-release -confirm-license -platform win32-msvc2015 -opengl desktop -static -nomake examples -no-compile-examples -nomake tests -prefix C:\Qt\static\MSVC2015_Static_x64 -openssl -L C:\OpenSSL-win64\lib -l libeay32 -l ssleay32 -I C:\OpenSSL-win64\include -qt-libpng -qt-libjpeg -qt-zlib
    

    Also definitely verified win32-msvc2015 was in the mkspecs directory. I couldn't find much on Google so I post here in hope of help. Thanks. I'm hoping it's simple like I left out a directory to put in the path environment variable...

    jsulmJ 1 Reply Last reply
    0
    • C Offline
      C Offline
      Crag_Hack
      wrote on last edited by
      #4

      Turns out the problem was I renamed the QT static build directory after the build, which broke it. Quick fix: rename it to its original configure -prefix name.

      1 Reply Last reply
      0
      • C Crag_Hack

        I'm having trouble using my QT 5.7 MSVC 2015 static builds, both 32-bit and 64-bit. This is the commands I run and the output I get (tested with 32 bit as well):

        C:\Users\Josh>set PATH=C:\Qt\static\Qt 5.7.0 MSVC2015_Static_x64\bin;%PATH%
        
        C:\Users\Josh>cd "\Users\Josh\Mozy Sync\ReplicatorNew\ReplicatorNew"
        
        C:\Users\Josh\Mozy Sync\ReplicatorNew\ReplicatorNew>qmake ReplicatorNew.pro
        Could not find qmake configuration file win32-msvc2015.
        Error processing project file: ReplicatorNew.pro
        

        Configure was run with the following:

        configure -debug-and-release -confirm-license -platform win32-msvc2015 -opengl desktop -static -target xp -nomake examples -no-compile-examples -nomake tests -prefix C:\Qt\static\MSVC2015_Static_x86 -openssl -L C:\OpenSSL-win32\lib -l libeay32 -l ssleay32 -I C:\OpenSSL-win32\include -qt-libpng -qt-libjpeg -qt-zlib
        
        configure -debug-and-release -confirm-license -platform win32-msvc2015 -opengl desktop -static -nomake examples -no-compile-examples -nomake tests -prefix C:\Qt\static\MSVC2015_Static_x64 -openssl -L C:\OpenSSL-win64\lib -l libeay32 -l ssleay32 -I C:\OpenSSL-win64\include -qt-libpng -qt-libjpeg -qt-zlib
        

        Also definitely verified win32-msvc2015 was in the mkspecs directory. I couldn't find much on Google so I post here in hope of help. Thanks. I'm hoping it's simple like I left out a directory to put in the path environment variable...

        jsulmJ Offline
        jsulmJ Offline
        jsulm
        Lifetime Qt Champion
        wrote on last edited by
        #2

        @Crag_Hack Does this path contain blanks?

        PATH=C:\Qt\static\Qt 5.7.0 MSVC2015_Static_x64\bin;%PATH%
        

        You should avoid such paths or at least use "":

        PATH="C:\Qt\static\Qt 5.7.0 MSVC2015_Static_x64\bin";%PATH%
        

        Another thing C:\Qt\static\MSVC2015_Static_x64 is different to C:\Qt\static\Qt 5.7.0 MSVC2015_Static_x64

        https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply
        1
        • C Offline
          C Offline
          Crag_Hack
          wrote on last edited by
          #3

          Thanks jsulm. I get the same results with quotes as without. Also I renamed those configure dirs after the build completed. See here:

          C:\Users\Josh>set PATH="C:\Qt\static\Qt 5.7.0 MSVC2015_Static_x86\bin";C:\Qt\5.7\msvc2015;%PATH%
          
          C:\Users\Josh>cd "\Users\Josh\Mozy Sync\ReplicatorNew\ReplicatorNew"
          
          C:\Users\Josh\Mozy Sync\ReplicatorNew\ReplicatorNew>qmake ReplicatorNew.pro
          Could not find qmake configuration file win32-msvc2015.
          Error processing project file: ReplicatorNew.pro
          

          I decided not to use quotes because other guys in my path didn't either like this fellow:

          C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
          

          Also I've been having trouble installing the "common tools" guy even after a complete VS uninstall and reinstall if it makes a difference... After I install when I go back to the change install screen below it never persists. I thus have no access to the VS command prompt shortcuts and have been forced to use vcvarsall.bat.

          alt text

          1 Reply Last reply
          0
          • C Offline
            C Offline
            Crag_Hack
            wrote on last edited by
            #4

            Turns out the problem was I renamed the QT static build directory after the build, which broke it. Quick fix: rename it to its original configure -prefix name.

            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