Installation and Deployment

@jsulm wow! i use the absolute path, so it works? [image: 4acdeea6-0d56-44d6-93a8-62d4d5dd3c8c.png]

@burjuvanzi Up to you, but you could at least try 14.04 or even 12.04 instead of 11.04...

@chris1092387456 could it be possible you have mixed Qt versions from the one you cross-compiled and the one it's used by the OpenCV install script you used. Assuming you run Ubuntu/opencv_latest.sh which in turn calls opencv_install.sh and then dependencies.sh, there are some apt-get install calls, so you''ll end up having pre-built Qt libraries along with your cross-compiled ones... function install_dependency { echo "--- Installing dependency: $1" sudo apt-get -y install $1 } ... install_dependency libqt5x11extras5 install_dependency libqt5opengl5 install_dependency libqt5opengl5-dev So may I suggest to start from scratch? First I'd follow the mechatronics guide to cross-compile and deploy Qt in the RPi device. Then I'd follow this guide to cross compile the latest version of OpenCV for Raspberry Pi. As you'll use WITH_QT=ON flag I guess, please adjust the paths in the CMake script(s) to use the cross-compiled Qt version in your host PC. And also use the correct path for cross-compiled OpenCV in your .pro file. As example, the following doesn't look good to me: LIBS += -L/usr/local/lib/libopencv_highgui.so

@jwall141 well, than there's only one way. Run the deploy tool and manually replace the dlls with the correct ones. The Deploytool should copy all needed files, even if they are from the wrong wt installation

@saeid said in Where to find qt-sdk: I am running Lubuntu 19.04 on a mini-pc. I am developing an application on my desktop and want to deploy it on a mini-pc (both use the same architecture and binary compatible). I want to avoid installing the whole qt (5.13) on the mini-pc. I remember in good old days it was enough to install 'qt-sdk' package...but I can not find that anymore... Any ideas how to manage this? sudo apt install qt5-qmake or on some systems: sudo apt install qt5-default That will install the Qt libraries (not Qt Creator). But if you really only want to deploy a working executable to your other machine, you should use proper deployment tool: create a DEB package or create an AppImage (or a Snap, or Flatpak), or compile statically. Some more info in the docs: https://doc.qt.io/qt-5/linux-deployment.html

Hi, Now I have got all dependencies fixed and there is no error, I am building now... Thanks a lot for your support. Regards Kumar

@jsulm I finally got working, somehow So the way I first built the project was this: cd path/to/project/with/pro/file C:\Qt\WABuild\qt-everywhere-src-5.13.0\qtbase\bin\qmake.exe && mingw32-make Which is the way described in the "Qt for WebAssembly" page, but then I did this instead: C:\Qt\WABuild\qt-everywhere-src-5.13.0\qtbase\bin\qmake.exe path/to/project/with/pro/file && mingw32-make.exe And now it works! I'm not really sure why these two are different, but at least it works. Thanks for the help.

Hi. I pretty much cross-compile everything for my many PIs using multiple versions of Qt (although 5.13.0 seems to work rather nicely). I run a Fedora host, although there is no reason this shouldn't work equally as well on any other distro. (If you're running Windoze you're on your own ;) It took a bit at first. I have a script at https://github.com/StevePunak/KanoopCommonQt/blob/master/docs/configqt which I use to do my initial configuration. Modify the locations at the top to suit your build system, then run this script from your new shadow build location to do your configure Three big tips to avoid unnecessary pain are: Never build in source. Always use a shadow directory. Wherever you have the Qt source, make a directory for the build at the same level as Src/, and build there. You can rm -rf the contents of this shadow directory to get a complete clean Before you even start trying to build, fix the symbolic links on your PI directly by using the symlinks utility 'apt-get install symlinks' and running 'sudo symlinks -c .' in /usr/lib/arm-linux-gnueabihf and /etc/alternatives' If possible, DO NOT create a sysroot on your host. Instead use sshfs to mount your PI and use that as your sysroot. That way you will always be in sync when you install new dev packages on your PI. I can not tell you how much time that has saved me! Hope this helps a little

That's a good question, I think you should contact the Cygwin Qt package maintainer(s). They should be able to help you ore efficiently.

Changing the '\' to '/' in QtStaticDir (e.g. from C:\Qt\5.13.0\mingw73_64_static to C:/Qt/5.13.0/mingw73_64_static) did not work for me. I'm having the same problem using Windows 10 x64, Qt 5.13.0 and MinGW 7.30 64-bit So we have established that the problem is not specifically with the 5.12.3 version of Qt (5.13 is affected too), nor the 32-bit version of MinGW (the 64-bit version is affected too). It is unfortunate that the bug report in bug tracker was closed (twice!): https://bugreports.qt.io/browse/QTBUG-68502 https://bugreports.qt.io/browse/QTBUG-72585 The claim by the person who closed it was that this is not a Qt problem. There is clearly an issue with the way Qt sources interact with the compiler that Qt is distributing, affecting users who follow the instructions on static builds that are given on the official Qt website: this sounds a "Qt problem" to me, even if "it's someone else's fault". I'll keep trying to find a solution and post back here.

Alright, I uninstalled Qt and re-installed it. I must have deleted the directory somehow. I can see it now.

IIRC, Qt already provides a set of translation files you can use in your application for the pre-built controls like that.

@J.Hilk Thank you. Can you please help me with cmake. How do i set the cmake for desktop (5.12.4 MinGW-64 bit) . Currently when i create the ArcGIS QML app and run through the desktop kit it says "error: FS/No such file or directory".[image: 75ecd10a-5fd7-4dcc-973f-e662739c1485.png]

@vaibs1224 said in How to install Qt in windows 10?: C:/Qt1/Tools/mingw730_32/bin/mingw32-make This is the wrong compiler. Install a suitable MinGW compiler as @mrjj pointed out above. Regards

@SGaist when we tried to use a list of values, it didn't work for us: This application failed to start because it could not find or load the Qt platform plugin "minimal;xcb" in "". Available platform plugins are: minimal, xcb.

@JDePedro Ok. I found the cause why I was not getting anything QML related from the tool. My widget is not in the exe file but in a DLL so I had to specify the dll instead. But the list of files the tool is getting is huge compared with the one I got by doing the process "manually" and includes most of the .qml files. So my doubt is, do we need to deploy all this files with my application? is not enough with the dlls???

@anshah Did you copy xcbglintegrations directory like described here: https://github.com/probonopd/linuxdeployqt/issues/150 ? This tool could simplify your life: https://github.com/probonopd/linuxdeployqt

@rooted so please mark your post as such! Thanks.