@oblivioncth I can confirm that this was fixed in 6.0.1

So everything looks correct... How are you loading your image in your application ?

@jsulm Uhmm now I'm starting to understand why @sierdzio told me this is not easy. I will do some google search on this subject, thanks for guidance.

Great ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :-) In case, there's an answer that provides the correct hint, you can also use the three button menu to mark it as the correct answer.

@Christian-Ehrlicher said in Why it is generating multiple library files instead of single file?: why does your user has to link to all 4 files, esp. when three of them are (correct) symlinks? Sorry for silly question. I misunderstood about symbolic link. I got my answer user need to add libSquidstatLibrary.1.0.0.dylib file. Thank you.

@JG97 said in QT 5.8.0 64 Bit with MinGW-w64 Configuration: How do I configure the x86 package for building 64 bit applications? You can't. You install Qt 5.12 MinGW 64bit and MinGW 64bit (it is available in the installer under Tools) and use this for 64bit apps. For 32bit apps you do the same but 32bit...

@sierdzio Thank you. Will look into it.

I have found a solution here. Looks like Ubuntu couldn't run 32bit binary, but it's working now.

Ok... well it seems now that the answer is that I need to use -prefix <> option.

I also stuck in that place with error: Project ERROR: Cannot run target compiler '<path>/arm-linux-gnueabihf-g++'. but indeed as @aha_1980 said: @aha_1980 said in Compiling QT on windows for cross compilation with raspberry, fails. Project ERROR: Cannot run target compiler: Maybe you forgot to setup the environment? The best checkout if compiler is accessible is to run in root dir where Qt sources are: // with entry in bashrc $ arm-linux-gnueabihf-g++ --version //or with absolute path: $ /home/<user_name>/<path-to-bin-where-compiler-is-located>/arm-linux-gnueabihf-g++ --version NOTE: replace <user_name> with your's user name, and replace <path-to-bin-where-compiler-is-located> with proper path as stated below. And then we should get info: arm-linux-gnueabihf-g++ (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) 4.8.3 20140303 (prerelease) ... The problem was with path to compiler: paths with "~" don't work, the best is to provide absolute path, for example: /home/<user_name>/<path-to-bin-where-compiler-is-located> // in my case: /home/<user_name>/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin Or add in .bashrc path to compiler by adding at the end of file: export PATH=$PATH:/home/<user_name>/<path-to-bin-where-compiler-is-located> // in my case: export PATH=$PATH:/home/<user_name>/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin Then running configure script we have: with absolute path: $ ./configure <other options> -device-option CROSS_COMPILE=/home/<user_name>/<path-to-bin-where-compiler-is-located>/arm-linux-gnueabihf- <other options> // in my case: $ ./configure <other options> -device-option CROSS_COMPILE=/home/<user_name>/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf- <other options> with entry in bashrc: $ ./configure <other options> -device-option CROSS_COMPILE=/home/<user_name>/<path-to-bin-where-compiler-is-located>/arm-linux-gnueabihf- <other options> //in my case: $ ./configure <other options> -device-option CROSS_COMPILE=arm-linux-gnueabihf- <other options> Tested on RPi3 (with Raspbian from 2019-09-26) and Qt 5.12.6, on Ubuntu 18.03.4 Cheers!

I was able to solve the problem where fontconfig was not able to find libexpat by adding the following in my xplatform qmake.conf QMAKE_LINK = $HOST-g++ -lts -L/opt/qt/qt5.9.1arm/lib -Wl,-rpath -Wl,/opt/qt/qt5.9.1arm/lib QMAKE_LINK_SHLIB= $HOST-g++ -lts -L/opt/qt/qt5.9.1arm/lib -Wl,-rpath -Wl,/opt/qt/qt5.9.1arm/lib

Thanks @J-Hilk The link provided needs other configuration. My machine configuration is Red Hat Linux - 32 bit Qt creator 1.2.92, based on Qt 4.6.0 (32 bit) Make version: GNU Make 3.81 Qmake version: 1.07a (Qt 3.3.6) Please let me know what are the pre-requisites for a plugin. I want to create a menu item for Qt creator. Thanks in advance.

You're welcome ! I'm pretty sure not all these packages are necessary but at least you have it working now :)

@kfrosty Thank you! Did work for me too! :)

You have here a list of the modules and their state. QtWebkit as been deprecated and removed. QtQuick1 as been deprecated and removed You can still build them from sources but you have to clone them specifically.

@SGaist Thanks. Seems like that is exactly what i need.

@AliReza-Beytari Ps. are you sure this works with 5.7 ? Only Qt 5.6 is mentioned.

@Mark81 it's a compiler issue: https://github.com/raspberrypi/tools/issues/41

Just saw something, why are you using sudo ? That's not a good idea when you are building anything.

I didn't try. 5.4.1 is enough for me

@The2Ring welcome to devnet forum I have not done a build of Qt libs myself for some time. Therefore, I am not completely sure, but the building scripts are typically not happy about the use of backslashs '\'. Those are certainly the main folder separators for windows, but may need escaping. The scripts of Qt are originally coming from linux. Therefore in a lot of places it is better to use the forward slash '/' instead. I have seen that you have used already the forward slash with LIBS and INCLUDEPATH. So you are aware of the issue. However, you have used with configure.bat back slashes. In my opinion it is certainly worth a try with forward slashes. This is sometimes as a miracle and solving issues which are hard to understand.

@Bart_Vandewoestyne said: we're storing our Qt build in our version management system This is a strange thing to do, since Qt guarantees binary compatibility between minor versions, but well, you're free to choose. Unfortunately, I don't see how you could decrease the size further, beside deleting the docs, as the libraries are in the /lib directory and they're the next biggest size. Maybe store only the libs that you're using, i.e. these that you're going to deploy. No point in keeping QtXml if you're not using it, right?

@Mike_Blackman said: My application fails to load libqxcb.so plugin, because libqxcb.so plugin fails to locate Qt libraries. Prebuilt Qt solves this problem by using relative RUNPATH value within libqxcb.so. Sorry, I don't know what the prebuilt libraries did to the RPATH/RUNPATH. You can ask the Qt engineers in the Interest mailing list: http://lists.qt-project.org/mailman/listinfo/interest (Subscribe to the list first, then post there)

@Ajith_P_V Yes that is right, you don't need to add the physical device. That was really just an extra option in case that was convenient to you later on : ) Have a look at creating kits for cross compiling in the qt docs if you can find it! - there are quite a few bits of info out there that may fill in the gaps I have left. I only gave the general steps required.

@JKSH Thank you very much for your answer, I've successfully built Qt using your tutorial!

Back on topic. I found that when building Qt you can specify to build only the module you need at the nmake stage, e.g. nmake module-qtbase That way it won't try and build all the other modules and qml libs.

Solved. Just started compiling 5.4.2 and just small issues that are easier to resolve.

Hi and welcome to devnet, you can create your Project Wizard in Qt Creator

No, I don't have any problem with build environment. I want to know the list of parameters. For example like in Xcode.

@sierdzio said: Thanks a lot for the clarification.

IIRC, QtCore will also use pcre for QRegularExpression