Talk:Building a static Qt for Windows using MinGW: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 5: Line 5:
using the static path, and "build and run kit selector" does not offer the static option created.
using the static path, and "build and run kit selector" does not offer the static option created.
Could someone test this howto and update it thanks. --[[User:Timsoft|Timsoft]] ([[User talk:Timsoft|talk]]) 17:01, 13 September 2015 (UTC)
Could someone test this howto and update it thanks. --[[User:Timsoft|Timsoft]] ([[User talk:Timsoft|talk]]) 17:01, 13 September 2015 (UTC)
I found that the "windows-build-qt-static.ps1" script faulted at line 166. The call to configure.bat had a -qt-sql-sqlite argument that was unsupported on my system. Deleting this argument allowed me to run the script again and get successful completion.

Revision as of 11:36, 1 January 2021

The correct environment path data in the section 'Command line' must be updated. I didn't know all the exact data. Peter (talk) 09:42, 8 July 2015 (UTC)

Actually the current script will try to get 5.3.1 if not given other version number. I just finished building static Qt with some custom configurations. Default Directory would be: $QtStaticDir\$QtVersion, which would default (w/ 5.5) C:\Qt\5.5. Source will be extracted default to $QtStaticDir\src NetZwerg (talk) 11:15, 8 July 2015 (UTC)

In Section "Using the QT Static environment with Qt Creator", the path to browse to is invalid. it does not refer to the c:\qt\static\5.5.0\bin path where the "static qmake" files reside, or to the c:\qt\qt5.5.0\5.5\mingw492_32\bin path of the dynamic qmake. using the static path, and "build and run kit selector" does not offer the static option created. Could someone test this howto and update it thanks. --Timsoft (talk) 17:01, 13 September 2015 (UTC)

I found that the "windows-build-qt-static.ps1" script faulted at line 166. The call to configure.bat had a -qt-sql-sqlite argument that was unsupported on my system. Deleting this argument allowed me to run the script again and get successful completion.