How I change qmake configuration. In all projects which I make, qmake puts -fno-exceptions -fno-rtti -DQT_NO_DYNAMIC_CAST flags in Makefile.Realease and other undesirable flags. How I can change this behavior.
I am on Windows. I use mingw-64 (ruben build). I used the following commands to build qt 4.8.3:
..\src\configure.exe -opensource -confirm-license -plugin-sql-mysql -plugin-sql-sqlite -no-dsp -no-vcproj -no-qt3support -no-phonon -no-phonon-backend -platform win32-g++ -largefile -fontconfig -no-webkit -nomake examples -nomake demos -prefix "D:\qt\4.8.3\x86_64-w64-mingw32" -I "D:\mysql\include" -L "D:\mysql\lib" -l mysql
make
make install
Does it help when you add exceptions and rtti to your CONFIG variable?
CONFIG += exceptions rtti
You should probably make sure that your custom Qt build has exception and rtti support enabled:
configure.exe -exceptions -rtti [...]
Related
My ssd died and I had to reinstall Qt, Im using the same version as before (5.15.2, Qt Creator 6.0.2 and MSVC2019). Described problems appears only while using Static build.
This type (ApplicationWindow) is not supported as a root (Im not 100% sure if it was fine before reinstall)
Invalid property name "title, maximumHeight, maximumWidth, minimumHeight, minimumWidth".
And finally after resolving (Changed from ApplicationWindow to Window, and commented Invalid Properties) these two errors I got: Line 1: Qt Quick emulation layer crashed. I attached a debugger to Qt Creator and it's 0xC0000005 on Editor, Preview and Render.
I tested it in both ways, with latest Qt Creator (installed before making Static kit because it will wipe my Qt directory) and with Qt Creator 6.0.2 (installed after making Static kit).
To compile Static Kit I used this script, but after some problems (jom and jom install did not create any files in QtInstallDir) I just run configure.bat by myself, and then jom and jom install and files were in their place.
The solution can be:
Designing using diffrent kit with Window and then on release change Kit to static, change Window to ApplicationWindow (Im using onClosing from ApplicationWindow).
but it's dirty and I personally do not like it. Is there any other solution?
EDIT: non-static versions are fine (self-compiled and one from MaintenanceTool).
Static configure.bat:
configure.bat -prefix %QTINSTALLDIR% -platform %PLATFORM% -opensource -debug-and-release -confirm-license -opengl dynamic -mp -static -static-runtime -no-shared -qt-libpng -qt-libjpeg -qt-zlib -qt-pcre -no-compile-examples -nomake examples -no-icu -optimize-size -qt-sqlite -openssl-linked OPENSSL_PREFIX=%SSLINSTALLDIR%
Non-static configure.bat:
configure.bat -prefix %QTINSTALLDIR% -platform %PLATFORM% -opensource -debug-and-release -confirm-license -opengl dynamic -mp -no-compile-examples -nomake examples -optimize-size -qt-sqlite
Diffrence:
-static -static-runtime -no-shared -qt-libpng -qt-libjpeg -qt-zlib -qt-pcre -openssl-linked OPENSSL_PREFIX=<location>
Okay, I fixed the Invalid property name .., I dont know what really fixed it but:
I had wrong versions of requirements. I was on latest of Ruby, Python etc.
I installed Submodules one more time using script linked in main post and then installed them one by one by my own hands using qmake then jom clean all then jom install.
Also I found that the Line 1: Qt Quick emulation layer crashed. error appear only when I have QtQuick.Controls <any_version> in imports. Im still trying to fix this.
Fixed. I did this by doing those steps:
In maintenance tool I downloaded Mingw64 and Mingw64 for 5.15.2 and for "Tools".
I did an static mingw build using this powershell script: https://wiki.qt.io/Building_a_static_Qt_for_Windows_using_MinGW
I saw that the script is changing qmake.conf files in mkspecs folder. I ran this MSVC script to make MSVC Static build and after unzipping QtBase I modified qmake.conf in mkspecs/winrt-x64-msvc2019 and in mkspecs/win32-msvc.
QMAKE_LFLAGS += -static
QMAKE_CFLAGS_RELEASE -= -O2
QMAKE_CFLAGS_RELEASE += -Os
DEFINES += QT_STATIC_BUILD
Then the qt setup and qt build command, when build is finished I modified the (THIS TIME IN PREFIX LOCATION / LOCATION WHERE QT STATIC IS INSTALLED) qmake.conf in mkspecs/winrt-x64-msvc2019 and in mkspecs/win32-msvc
CONFIG += static
Run Qt Creator and the Designer is fine.
Couldn't find answer myself.
I try to use a power shell script windows-build-qt-static.ps1 to build QT from sources. It's did not working as is, so I modify it. I have download sources manualy, unzip them, place into properly dirrectory, manually patch mkspecs with
# [QT-STATIC-PATCH]
QMAKE_LFLAGS += -static -static-libgcc
QMAKE_CFLAGS_RELEASE -= -O2
QMAKE_CFLAGS_RELEASE += -Os -momit-leaf-frame-pointer
DEFINES += QT_STATIC_BUILD
and finally I start the power shell script, which contains only following part (the rest code I had remove):
$MingwDir = "c:\Qt\Qt5.7.0\Tools\mingw530_32\"
$QtDir = "c:\Qt\Static\5.7\"
$QtSrcDir = "c:\Qt\Static\src\"
# Set a clean path including MinGW.
$env:Path = "$MingwDir\bin;$MingwDir\opt\bin;$env:SystemRoot\system32;$env:SystemRoot"
# Force English locale to avoid weird effects of tools localization.
$env:LANG = "en"
# Set environment variable QT_INSTALL_PREFIX. Documentation says it should be
# used by configure as prefix but this does not seem to work. So, we will
# also specify -prefix option in configure.
$env:QT_INSTALL_PREFIX = $QtDir
# Configure, compile and install Qt.
Push-Location $QtSrcDir
cmd /c "configure.bat -static -debug-and-release -platform win32-g++ -prefix $QtDir `
-qt-zlib -qt-pcre -qt-libpng -qt-libjpeg -opengl desktop -qt-sql-sqlite -no-openssl `
-make qtserialport -make libs -nomake tools -nomake examples -nomake tests"
mingw32-make -k -j4
mingw32-make -k install
Pop-Location
# Patch Qt's installed mkspecs for static build of application.
$File = "$QtDir\mkspecs\win32-g++\qmake.conf"
#"
CONFIG += static
"# | Out-File -Append $File -Encoding Ascii
After that, I have compiled QT sources in static libraries, but only following:
This compiled libraries doesn't contains the needed for me (qtserialport, qtcharts, qtconnectivity and other).
Then, I realized, that the mingw32-make is misconfigured, but I can found that lines in main Makefile:
...
module-qtserialport-qmake_all: module-qtbase-qmake_all FORCE
#if not exist qtserialport\ mkdir qtserialport\ & if not exist qtserialport\ exit 1
cd qtserialport\ && $(QMAKE) C:\Qt\Static\src\qtserialport\qtserialport.pro -o Makefile
cd qtserialport\ && $(MAKE) -f Makefile qmake_all
module-qtserialport: module-qtbase FORCE
#if not exist qtserialport\ mkdir qtserialport\ & if not exist qtserialport\ exit 1
cd qtserialport\ && ( if not exist Makefile $(QMAKE) C:\Qt\Static\src\qtserialport\qtserialport.pro -o Makefile ) && $(MAKE) -f Makefile
module-qtserialport-make_first: module-qtbase-make_first FORCE
#if not exist qtserialport\ mkdir qtserialport\ & if not exist qtserialport\ exit 1
cd qtserialport\ && ( if not exist Makefile $(QMAKE) C:\Qt\Static\src\qtserialport\qtserialport.pro -o Makefile ) && $(MAKE) -f Makefile
...
I try found out, why many modules did not compile. I tried compile them manually, but I`m failed.
Please help me compile whole Qt Creator (with all modules) into static libs, or build each module as static lib manually.
The build in later Qt versions has been more simplified, no patching is required anymore instead you can use -static-runtime.
If you want to build Qt 5.7.0 the steps are as following:
Download the source code and extract it
Open your developer console (MingW or MSVC) and navigate to the folder
Type configure -static -static-runtime -debug-and-release -prefix /your/directory -no-openssl -nomake tools -nomake examples -nomake tests(add additional features, if you want)
mingw32-make -k -j4 (or jom/make)
mingw32-make -k install (or jom/make)
The shell script was helpful in earlier versions where you had to patch certain variables.
What is the correct way to use -prefix -extprefix and -hostprefix options to cross compile Qt5?
I have sysroot dir for my arm board. And I have no problems with cross compiling Qt for ARM except one - I can't figure out how to specify installation path to directory on my host machine (not whitin sysroot). Every combination of -[..]prefix flags trying to install Qt on board. There is not much disk space on board, so I want install Qt locally.
It's my current config:
./configure -opengl es2 -nomake tests -no-libjpeg -skip qtwebkit -skip qtwebkit-examples -no-xcb -device linux-jetson-tk1-g++ -device-option CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- -sysroot /mnt/jetson_tk1_sysroot -hostprefix /home/alan/work/qt/qt_5.5.1_arm_cross_compiled -make libs -debug -v
I'm already read this SO topic, Qt docs and google a lot.
I'm running Ubuntu on both host and target if it's matter.
Install step targets the directory specified by extprefix which is optional and defaults to sysroot/prefix. Defining extprefix to point some directory in the host should prevent you from polluting your sysroot. hostprefix allows separating host tools like qmake from target binaries. When given, such tools will be installed under the specified directory instead of extprefix.
Using these prefix flags keeps your sysroot clean and separates device binaries and host tools:
export INSTALLPATH=/home/alan/work/qt/qt_5.5.1_arm_cross_compiled
./configure ... -extprefix $INSTALLPATH/binaries -hostprefix $INSTALLPATH/tools
On my Windows 7 SP1 machine I would like to use Qt in Visual Studio and compile Qt projects with Visual Studip with static linking,to be able to share my projects in a single .exe file.
Since there are no precompiled libraries for Visual Studio 2017 32bits (although they exists for x64),i'm going to compile Qt from sources.
Following Qt's documentation,I started by installing Python 2.7.13 and Active-Perl,and adding their installation path to the PATH variable,along with the gnuwin32/bin folder
Then i created a qt5vars.cmd file under C:\Qt,here's his content :
REM Set up \Microsoft Visual Studio 2017, where <arch> is \c amd64, \c x86, etc.
CALL "C:\Program Files\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" x86
SET _ROOT=C:\Qt\5.9.1
SET PATH=%_ROOT%\qtbase\bin;%_ROOT%\gnuwin32\bin;%PATH%
REM Uncomment the below line when using a git checkout of the source repository
#REM SET PATH=%_ROOT%\qtrepotools\bin;%PATH%
SET _ROOT=
And finally I unzipped Qt sources (downloaded from here to C:\Qt\5.9.1,and jom under C:\Qt\jom
I'm planning to use these commands (after executing qt5vars.cmd) to compile and install Qt :
configure -debug-and-release -opensource -platform win32-msvc2017 -static -nomake examples -nomake tests -prefix C:\Qt-5.9.1
jom -j 2
jom install
I already installed Qt vs tools in VS2017.
Is the procedure correct,or should I change something ? (particularly in the configure command)
Looks good. My only remarks would be:
To remove gnuwin32 path as I don't see a reason why would you need it.
And consider making a shadow build to keep Qt sources unpolluted.
set _SHADOW_DIR="C:\build_static"
set _SOURCE_DIR="C:\SrcQt5.9.1"
...
cd %_SHADOW_DIR%
call %_SOURCE_DIR%\configure ...
Run: "x86 Native Tools Command Prompt for VS 2017"
Or from console
%comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars32.bat"
Go to your Qt source dir "qt-everywhere-src-5.14.0/"
Run
configure -static -debug-and-release -prefix "f:\Qt\Static\build\5.14\build" -platform win32-msvc -qt-zlib -qt-pcre -qt-libpng -qt-libjpeg -qt-freetype -opengl desktop -qt-sqlite -sql-odbc -no-openssl -opensource -confirm-license -make libs -nomake tools -nomake examples -nomake tests -skip qtwebengine
After some hours run
nmake
Wait some hours again and run
nmake install
A lot of post about qtwebengine,ssl i simply disable this.
Hope this post help you save your expensive time.
I've been trying to get a static build of Qt 5.7 together so I can start compiling an application statically on Windows, but it's been a bit of a slog. I've got most of the process working - except it is complaining about not being able to include a file now that I can't see any reason for it to complain about.
I have to use MSVC (2015 is what is installed) and nmake because we're including webkit (which is possible with MinGW - and so we can't cross-compile from Linux either).
I've worked through and adapted the following sites (amongst others):
http://amin-ahmadi.com/2016/09/22/how-to-build-qt-5-7-statically-using-msvc14-microsoft-visual-studio-2015/
https://wiki.qt.io/Building_Qt_Desktop_for_Windows_with_MSVC
How do you compile OpenSSL for x64?
My configure command:
configure -debug-and-release -commercial -static -ltcg -accessibility \
-platform win32-msvc2015 -qt-sql-sqlite -qt-sql-sqlite2 \
-plugin-manifests -no-audio-backend -openssl -no-dbus \
-incredibuild-xge -sse2 -qt-style-windows -qt-style-fusion \
-no-native-gestures -qmake \
-I C:\devel\source\openssl\inc64
And right now it's complaining that it can't load "openssl\ssl.h" - except that this is available in C:\devel\source\openssl\inc64\openssl\ssl.h