Installation and Deployment

Based on the name, do you have any non-ASCII char in the path ?

@bcam Try to see my scripts https://github.com/r3d9u11/env-maker/tree/master/Qt/Qt5-imx6, I think that it can be used for RPi (just change gcc-8 to linaro compiler)

@JKSH Building my plugin with MSVC 2017 32-bit worked. Thank you.

It's likely related to QTQAINFRA-1187. There's currently no mention of the macOS platform. You should comment there to get some more information. In between, one thing you can try, is to build only the QPA plugin from sources.

@SGaist Tried it with the declarative-camera example, same result.

I cannot copy from my work computer to my internet computer. If I can get Qt Designer working at home I will draw it up and paste in an image. That will be tonight's task at home, getting QT to run on my Windows box. I am using Centos Linux here at work. In the meantime: Imagine widget A with size 600 wide by 300 high. It has a set of radio buttons, push buttons, line edits, etc. When I set values in A it creates SIGNALS directed to SLOTS in B. A will need at least 10 controlling widgets. Example: A spin box or line edit in A can change the update rate of the strip chart, how fast it scrolls. Imagine widget B with the same size just below A. Each has a border and can be grabbed and moved with the mouse. B is where the strip chart graphics will be displayed, done in Open Gl. It has a pushbutton labeled "Hide A" that will cause widget A to be hidden. When pressed it changes its name to "Show A" which does the obvious. I am quite new at both Qt and OpenGL so maybe this question is more simple that it at first appears. Maybe not. I get to jump in on the deep end.

Hi and welcome to devnet, Glad you found a solution and thanks for sharing it ! 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 :)

@mvelanka wow - good observation! glad you got it running. So please mark this topic as SOLVED now. Thanks!

@Sebastien_Pau Try http://www.dependencywalker.com/

@r3d9u11 Also pkg-config ouput: $ pkg-config --libs gstreamer-1.0 -L/mnt/data/LinuxHome/Software/QtBuilder/sysroot/lib -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 $ pkg-config --libs glib-2.0 -L/mnt/data/LinuxHome/Software/QtBuilder/sysroot/lib -lglib-2.0 $ pkg-config --libs zlib -L/mnt/data/LinuxHome/Software/QtBuilder/sysroot/lib -lz $ pkg-config --libs libpng -L/mnt/data/LinuxHome/Software/QtBuilder/sysroot/lib -lpng16 -lz $ pkg-config --libs libjpeg -L/mnt/data/LinuxHome/Software/QtBuilder/sysroot/lib -ljpeg $ pkg-config --libs fontconfig -L/mnt/data/LinuxHome/Software/QtBuilder/sysroot/lib -lfontconfig -lfreetype Note: /home/eugene/Desktop/QtBuilder/sysroot is a symlink to /mnt/data/LinuxHome/Software/QtBuilder/sysroot

@raven-worx Thanks a lot. Now, I got a perspective on how I can proceed further. I will try the solution with the QWebSocket and see how that goes. Cheers!

Hi @huseyinkozan Yes. It works like a charm. Regards, Mucip:)

solved :) thx for helping

@SGaist Well, I think no (if I understand your question right), because all paths to the compiler was setted right. Currently I'm trying to do a clean sysroot on my PC x86_64 (just a Qt+glib+gstreamer) with needed libraries (one question with pkg-config and Qt no resolved for me, yet) for the cross-compilation of target apps. As result I will produce a bash-script for a building an arm-sandbox to cross-compile from x86-64 machine to the ARM (specially imx6) and publish it here. Also thank you for your leading questions (because really currently available in the Ubuntu repos version of compiler is deprecated, I think)!

Did you do a cleanup before calling configure again ?

It took a while, but I have now solved this problem so let me share the solution that I found. I did a combination of the following three things to made it work: I needed a single cdUp() for the deployment situation as opposed to the 3x cdUp() which is necessary when running from Qt Creator (as it is explained here http://doc.qt.io/archives/qt-4.8/qt-tools-plugandpaint-example.html but on http://doc.qt.io/archives/qt-4.8/deployment-mac.html it says to use only 1x cdUp()) I was lead to believe that the argument for QDir::cd() would be case insensitive on MacOS based on the referred documentation. Instead, I now used 'PlugIns' instead of 'plugins' to use the standard directory in the app bundle to store my plugins in. I did so because using cd in a Terminal also required using 'PlugIns' instead of 'plugins'. On the other hand, when running from QtCreator, it should be 'plugins' as that is the subdirectory that QtCreator creates when building. So, here is a second difference between running from QtCreator and when deploying I not only applied install_name_tool to my executable to fix the library references but I also applied it to my plugin libraries. I made sure to use @executable_path references only to my libdfmcore and also to the Qt framework libraries (so, no @rpath references as generated by a build from QtCreator or by macdeployqt) If you wish to inspect my solution in more detail, you can have a look at https://modeltech.org/download/dfm/dfm.macos.zip