Cross-compiling RPi application using Qt Creator

Pablo J. Rogina

@Pavel_47 you may want to try this guide, in particular the section to setup Qt Creator

Pavel_47

Hello,
I plan to use Windows machine for that.
Does exist similar manual that elaborates flow for windows host ?
Thanks.

Pablo J. Rogina

@Pavel_47 said in Cross-compiling RPi application using Qt Creator:

I plan to use Windows machine for that.

Ok, not a good idea in my opinion... You may want to use a VM with Linux instead.

Given that said, and assuming that you already setup the cross-compiling environment on Windows per this guide (it's related to the guide you mentioned in your first post) then setting up Qt Creator to use such cross-compiling toolchain/environment can be followed from the guide I pointed out. At Qt Creator level, it's most the same (obviously the paths will change slightly...). Good luck.

Pavel_47

For building windows tools, manual specifies the following command:

mkdir qt-build
cd qt-build
../qt-everywhere-opensource-src-5.5.0/configure -platform win32-g++ -xplatform linux-arm-gnueabi-g++ -release -opengl es2 -device linux-rasp-pi2-g++ -sysroot C:/SysGCC/Raspberry/arm-linux-gnueabihf/sysroot -prefix /usr/local/qt5

For RPi3 device I should probably use linux-rasp-pi-g++ instead of linux-rasp-pi2-g++. Correct ?

Pavel_47

Here is the message what I get after executing build command:

The OpenGL ES 2.0 functionality test failed!
 Use of pkg-config is not enabled, maybe you want to pass -force-pkg-config?
 You might need to modify the include and library search paths by editing
 QMAKE_INCDIR_OPENGL_ES2, QMAKE_LIBDIR_OPENGL_ES2 and QMAKE_LIBS_OPENGL_ES2 in
 c:/Users/pyo/Downloads/qt-everywhere-opensource-src-5.5.0/qtbase/mkspecs/devices/linux-rasp-pi-g++.

Any ideas ?

sierdzio

Device should be linux-rasp-pi3-g++ or if you want EGLFS with full OpenGL support, linux-rasp-pi3-vc4-g++

Pavel_47

With linux-rasp-pi3-g++ I get this:
Error: No device matching 'linux-rasp-pi3-g++'

Pavel_47

sierdzio

Oh, Qt 5.5? Yes, that came out before Raspberry Pi 3 was on the market. I strongly recommend compiling a more modern version of Qt. Even Raspbian OS (which is veeery outdated) ships Qt 5.7...

Pavel_47

I took source from here:
qt-everywhere-src-5.12.3
Can you provide link with more recent version.
Thanks

Pablo J. Rogina

@Pavel_47 that's latest version so far

please be aware that a previous post from you has ../qt-everywhere-opensource-src-5.5.0/configure that's why I think @sierdzio brought that out.

Pavel_47

So, what about original problem: what location use in bulding command - linux-rasp-pi-g++ or linux-rasp-pi2-g++ ?

sierdzio

@Pavel_47 said in Cross-compiling RPi application using Qt Creator:

So, what about original problem: what location use in bulding command - linux-rasp-pi-g++ or linux-rasp-pi2-g++ ?

All your input so far suggest you are actually compiling Qt 5.5. Please make sure you're working with the 5.12.3 source you downloaded.

Pavel_47

Yes !!! Misunderstanding with my colleague - I believed that folder qt-everywhere-opensource-src-5.5.0 corresponds to the latest source of Qt. Indeed there are new device folder that correspond to RPi3: linux-rasp-pi3-g++ and linux-rasp-pi3-vc4-g++. What is the difference between them ?
Thanks.

Pavel_47

@Pavel_47 Ok, I see - OpenGL support

Pavel_47

Error while building !

Preparing build tree...
Creating qmake...
..............................c:/Users/pyo/Downloads/qt-everywhere-src-5.12.3/qtbase/src/corelib/global/qglobal.cpp:
In function 'QString qEnvironmentVariable(const char*, const QString&)':
c:/Users/pyo/Downloads/qt-everywhere-src-5.12.3/qtbase/src/corelib/global/qglobal.cpp:3346:49: error: '_wgetenv_s' was not declared in this scope
     _wgetenv_s(&requiredSize, 0, 0, wname.data());
                                                 ^
make.exe: *** [qglobal.o] Error 1

Pavel_47

Indeed, I've hierarchically searched for _wgetenv_s through whole qt-everywhere-src-5.12.3 (.cpp and .h) and found that it's referenced only in qglobal.cpp ... and declared/defined nowhere.

Pavel_47

On this link the author propose a workaround (although I'm not sure if this workaround is valid for my case).
Anyway I've added this instruction (i.e. defined MINGW_HAS_SECURE_API flag as suggested)
DEFINES += UNICODE _UNICODE WIN32 MINGW_HAS_SECURE_API=1
in ...\win32-g++\qmake.conf
Unfortunately it didn't help

Pavel_47

Well, I reported this issue as bug on
https://bugreports.qt.io/

sierdzio

Sounds like something that would not happen on Linux. I have never encountered this error, so I can only wish you luck :D