Talk:RaspberryPi2EGLFS: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(answered)
Line 106: Line 106:


EDIT: I don't know if you just want me to delete this. I found the problem. I was building for the pi2 and trying to run it on the pi zero. Sorry about that. I am new to this stuff. I figured out how to build for pi 1 / zero and now everything works. This is awesome!!!
EDIT: I don't know if you just want me to delete this. I found the problem. I was building for the pi2 and trying to run it on the pi zero. Sorry about that. I am new to this stuff. I figured out how to build for pi 1 / zero and now everything works. This is awesome!!!
== libinput not detected by configure script ==
Hi.
In this excellent tutorial it is said that one must make sure that libinput is set to "yes"
in configure's summary report.
I have libinput installed, and the library files are in the path, yet configure does
not detect it. Even when I add the -libinput argument to the configure command line.
The test widget however compiles and runs fine on my Pi2.
Is libinput really required, and why?
Thanks!

Revision as of 03:07, 9 May 2016

I got this error in make step


qeglfsbrcmintegration.cpp:35:22: fatal error: bcm_host.h: No such file or directory

#include <bcm_host.h>


compilation terminated.

make[6]: *** [.obj/qeglfsbrcmintegration.o] Error 1

make[6]: Leaving directory `/home/hamed/raspi/qtbase/src/plugins/platforms/eglfs/deviceintegration/eglfs_brcm'

make[5]: *** [sub-eglfs_brcm-make_first] Error 2

make[5]: Leaving directory `/home/hamed/raspi/qtbase/src/plugins/platforms/eglfs/deviceintegration'

make[4]: *** [sub-deviceintegration-make_first-ordered] Error 2

make[4]: Leaving directory `/home/hamed/raspi/qtbase/src/plugins/platforms/eglfs'

make[3]: *** [sub-eglfs-make_first] Error 2

make[3]: Leaving directory `/home/hamed/raspi/qtbase/src/plugins/platforms'

make[2]: *** [sub-platforms-make_first] Error 2

make[2]: Leaving directory `/home/hamed/raspi/qtbase/src/plugins'

make[1]: *** [sub-plugins-make_first] Error 2

make[1]: Leaving directory `/home/hamed/raspi/qtbase/src'

make: *** [sub-src-make_first] Error 2

hamed@hamed-PC ~/raspi/qtbase $

I edited this topic to add the solution to this error (fatal error: bcm_host.h: No such file or directory)

to solve this problem just add these lines

INCLUDEPATH += $[QT_SYSROOT]/opt/vc/include

INCLUDEPATH += $[QT_SYSROOT]/opt/vc/include/interface/vcos

INCLUDEPATH += $[QT_SYSROOT]/opt/vc/include/interface/vcos/pthreads

INCLUDEPATH += $[QT_SYSROOT]/opt/vc/include/interface/vmcs_host/linux

to these two files: "qtbase/mkspecs/devices/linux-rasp-pi-g++/qmake.conf"

and:

"qtbase/mkspecs/devices/linux-rasp-pi2-g++/qmake.conf"

after save the files repeat these two steps "configure" and "make"

the refrence is this thread



Different error in the make step http://stackoverflow.com/questions/34685488/qt-5-6-cross-compile-for-raspberry-pi-with-eglfs

QT Serial Port install in cross-compile environment

I am attempting to adapt the instructions linked here: Qt Serial Port to this cross-compile environment. The Qt Serial Port page suggests that Qt Serial Port is included in Qt5, however I cannot seem to find it. Has it been removed? I am running QT 5.4.2. on my host system.

If I have to install Qt Serial Port, then I am not sure how to successfully install it in this cross-compile environment. Can anyone help with this? Thank you!

Prerequisites to run cross compile tools on fresh Ubuntu/Debian x64

To run the tools on a host running Ubuntu / Debian x64, the following libraries are necessary:

$ sudo apt-get install lib32stdc++6 lib32z1 lib32ncurses5

Otherwise, errors like this might occur:

arm-linux-gnueabihf-g++: Command not found

or

arm-linux-gnueabihf-g++: Kommando nicht gefunden

--Woehrl.biz (talk) 08:06, 26 April 2016 (UTC)

X C Bindings

I had to add the following parameter to the configure command:

-qt-xcb

Otherwise the following error is shown:

The test for linking against libxcb and support libraries failed!
 You might need to install dependency packages, or pass -qt-xcb.
 See src/plugins/platforms/xcb/README.

--Woehrl.biz (talk) 09:42, 26 April 2016 (UTC)

Illegal instruction

I just set up a fresh Ubuntu 14.04 and RPiZero Raspbian.

I followed this tutorial and everything worked (after using the discussion page fixes) except for the example.

I built the example without errors, deployed it, set up the libraries, etc.

When I run the example on the Pi I simply get "Illegal Instruction". Nothing else.

I turned on logging and don't see the log output anywhere that I can find.

EDIT: I don't know if you just want me to delete this. I found the problem. I was building for the pi2 and trying to run it on the pi zero. Sorry about that. I am new to this stuff. I figured out how to build for pi 1 / zero and now everything works. This is awesome!!!

libinput not detected by configure script

Hi. In this excellent tutorial it is said that one must make sure that libinput is set to "yes" in configure's summary report.

I have libinput installed, and the library files are in the path, yet configure does not detect it. Even when I add the -libinput argument to the configure command line.

The test widget however compiles and runs fine on my Pi2.

Is libinput really required, and why?

Thanks!