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
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.
I am trying to compile qt with open ssl statically
I could compile openssl using vs2017 after install perl and configuring it
i used nmake and it worked with -no-shared smoothly.
Then i open the openssl folder and have the following
dll->x64->release>
bin
->c_rehash.pl
->libcrypto-1_1-x64.dll
->libcrypto-1_1-x64.pdb
->libssl-1_1-x64.dll
->libssl-1_1-x64.pdb
->openssl.exe
->openssl.pdb
include
openssl
header files
lib ->libcrypto.lib
->libssl.lib
->ossl_static.pdb
- engines-1_1 -> capi.dll
capi.pdb
padlock.dll
padlock.pdb
Then i opened VS command line
and opened Qt 5.12.4 coder
configure -static -openssl-linked -opengl dynamic -nomake tests -nomake examples -I "T:\openssl\dll\x64\release\include" -L "T:\openssl\dll\x64\release\lib" OPENSSL_LIBS="-lUser32 -lAdvapi32 -lGdi32 -lCrypt32"
I get the following:
error feature 'openssl-linked' was enabled but the pre-condition !features.securetransport && libs.openssl' failed
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
I try to compile Qt from sources, everything goes ok(more or less), except dbus part.
./configure -v -opensource -dbus-linked -arch i386
Configure shows this error:
1 error generated.
make: * [dbus.o] Error 1
D-Bus disabled.
The QtDBus module cannot be enabled because libdbus-1 version 0.93 was not found.
Turn on verbose messaging (-v) to ./configure to see the final report.
If you believe this message is in error you may use the continue
switch (-continue) to ./configure to continue.
I installed dbus 1.6 with Homebrew, but configure tool can't see it. Lib and headers are located in /usr/local/Cellar/d-bus/1.6.18. How to point configure to this location?
Platform is OS X.
Well the problem seems to be that, its not finding the dbus libraries.
Set the path of the library and the includes when you configure, something like this, assuming your dbus libraries and includes are in
/usr/local/Cellar/d-bus/1.6.18
./configure -v -opensource -arch i386 -dbus-linked -L/usr/local/Cellar/d-bus/1.6.18/lib -I/usr/local/Cellar/d-bus/1.6.18/include
where -I will tell qmake to include headers from that path and -L to link to the dbus libraries.
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 [...]