Talk:RaspberryPi2EGLFS: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(posted regarding a 'broken link' to a library.)
 
(11 intermediate revisions by 9 users not shown)
Line 1: Line 1:
'''I got this error in make step'''
== Asking Questions ==


Please post questions about building Qt for Raspberry Pi in the [https://forum.qt.io/ Qt forums].  This talk page can be used to talk about improving the article.


qeglfsbrcmintegration.cpp:35:22: fatal error: bcm_host.h: No such file or directory
== small fix to the relativelink fixing script ==
 
#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 [http://forum.qt.io/topic/62264/failed-to-cross-compile-qt-5-6-on-rpi-2-fatal-error-bcm_host-h-no-such-file-or-directory/3 thread]


The script relinks also systemd files pointing to /dev/null. Although this does not break anything currently, here is a fix
Copy the following and paste to shell in the directory where the sysroot-relativelinks.py is


patch <<'EOF'
*** sysroot-relativelinks.py~ Fri Apr 28 09:50:57 2017
--- sysroot-relativelinks.py Fri Apr 28 10:56:27 2017
***************
*** 18,23 ****
--- 18,25 ----
          return
      if link.startswith(topdir):
          return
+    if link.startswith("/dev/"):
+        return
      #print("Replacing %s with %s for %s" % (link, topdir+link, filep))
      print("Replacing %s with %s for %s" % (link, os.path.relpath(topdir+link, subdir), filep))
      os.unlink(filep)
EOF


== Ansible Roles/Playbooks Based on this Article ==


'''Different error in the make step'''
I used the instructions here to make Ansible playbooks that perform most of the same steps.  The playbooks can set up a Pi, set up a development computer, and then deploy Qt to the Pi.  Repo is https://bitbucket.org/johnwoltman/build_qt_for_pi_with_ansible
http://stackoverflow.com/questions/34685488/qt-5-6-cross-compile-for-raspberry-pi-with-eglfs


== QT Serial Port install in cross-compile environment ==
== Minor improvement to step 8 ==


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.
You can combine all 5 commands into one like this:


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!
rsync -avzR pi@raspberrypi.local:/lib :/usr/include :/usr/lib :/opt/vc sysroot


== Prerequisites to run cross compile tools on fresh Ubuntu/Debian x64 ==
Note that <tt>-R</tt> preserves the path names and that rsync creates the <tt>./sysroot</tt> directory for us.


To run the tools on a host running Ubuntu / Debian x64, the following libraries are necessary:<br />
Hi
$ sudo apt-get install lib32stdc++6 lib32z1 lib32ncurses5
I have Ubuntu 16.04 x64 and Qt Creator 5.10.1 x64 witch version of qt base should I choose?
for compile on raspberry pi 3 with Raspbian stretch x32 OS?


Otherwise, errors like this might occur:
== Recommended changes to Step #15 ==
arm-linux-gnueabihf-g++: Command not found
or
arm-linux-gnueabihf-g++: Kommando nicht gefunden
--[[User:Woehrl.biz|Woehrl.biz]] ([[User talk:Woehrl.biz|talk]]) 08:06, 26 April 2016 (UTC)


== X C Bindings ==
Just including the line:


I had to add the following parameter to the configure command:<br/>
  ./qopenglwidget
'''-qt-xcb'''


Otherwise the following error is shown:<br/>
So that way beginners (like me) know what to do to get it running.
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.
--[[User:Woehrl.biz|Woehrl.biz]] ([[User talk:Woehrl.biz|talk]]) 09:42, 26 April 2016 (UTC)


== Illegal instruction ==
== Suggestion of changes to step 14 ==


I just set up a fresh Ubuntu 14.04 and RPiZero Raspbian.
Make sure you're in "/home/pi" aka "~" when you run these commands:


I followed this tutorial and everything worked (after using the discussion page fixes) except for the example.
(This would have saved me an hour...)


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.
== Cross compilation on 64bit machines TIP ==
 
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.
Hi.
In this excellent tutorial it is said that one must make sure that libinput is set to "yes"
When You try to build QT on 64 bit PC without i386 libraries, use:
in configure's summary report.
  ~/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf-
 
I have libinput installed, and the library files and headers are in the sysroot path as required.
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!
 
== could not find or load the Qt platform plugin "eglfs" ==
 
After following the tutorial, when running qopenglwidget I get the following error:
 
This application failed to start because it could not find or load the Qt platform plugin "eglfs"
in "".
 
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, xcb.
 
Reinstalling the application may fix this problem.
Aborted
 
Since we are going to build Qt5 for Pi, I don't really get why
one must INSTALL certain modules of Qt BEFORE the build?


== Initial ==


Hi.
== Recommended changes to Step #4 ==


I just tried this tutorial on a Raspberry Pi 3, and encountered the following problem:
Honestly, `sudo rpi-update` should only be used by Raspbian developers to the firmware or operating system itself; it pulls from the `next` branch which is usually unstable. At times, it will brick your Raspi.


pi@raspberrypi:~ $ sudo apt-get build-dep libqt5gui5
Please change this to read `sudo apt-get update && sudo apt-get -y upgrade`. This will upgrade the operating system and yes, the firmware as well. It will pull from the stable `master` branch as expected.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Picking 'qtbase-opensource-src' as source package instead of 'libqt5gui5'
The following packages have unmet dependencies:
libgles2-mesa-dev : Depends: libegl1-mesa-dev but it is not going to be installed
libopenvg1-mesa-dev : Depends: libegl1-mesa-dev but it is not going to be installed
E: Build-dependencies for libqt5gui5 could not be satisfied.


Any hints?
==  error: undefined reference to `__cxa_throw_bad_array_new_length@CXXABI_1.3.8' ==


Thanks,
When try to build QT Creator app got an error:
OJ
raspi/sysroot/usr/lib/arm-linux-gnueabihf/libicui18n.so.57:-1: error: undefined reference to `__cxa_throw_bad_array_new_length@CXXABI_1.3.8'


Greetings to all from Argentina.
after some exploration add following line to .pro file:
I'm trying to install this OpenGL accelerator
QMAKE_LFLAGS += -fuse-ld=gold
I have a compilation with lots of errors how can I upload the text file with the screen output?
They are many pages of text.


Thank you very much.
Now its ok.


== small fix to the relativelink fixing script ==
== Add section about changed library names ==


The script relinks also systemd files pointing to /dev/null. Although this does not break anything currently, here is a fix
See [https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/ this] (part 6). I cite:
Copy the following and paste to shell in the directory where the sysroot-relativelinks.py is
"In new Raspbian stretch versions, EGL libraries have different names than those assumed in Qt configuration files, so edit the ./qtbase/mkspecs/devices/linux-rasp-pi*-g++/qmake.conf file and substitute all references to -lEGL and -LGLESv2 for -lbrcmEGL and -lbrcmGLESv2, respectively." (linux-rasp-pi*-g++ refers to the board you're using).


patch <<'EOF'
== Broken 'link' in Step 5 (part 2) ==
*** sysroot-relativelinks.py~ Fri Apr 28 09:50:57 2017
The qt4-x11 library has depreciated and is no longer available.
--- sysroot-relativelinks.py Fri Apr 28 10:56:27 2017
***************
*** 18,23 ****
--- 18,25 ----
          return
      if link.startswith(topdir):
          return
+    if link.startswith("/dev/"):
+        return
      #print("Replacing %s with %s for %s" % (link, topdir+link, filep))
      print("Replacing %s with %s for %s" % (link, os.path.relpath(topdir+link, subdir), filep))
      os.unlink(filep)
EOF

Latest revision as of 03:06, 9 August 2020

Asking Questions

Please post questions about building Qt for Raspberry Pi in the Qt forums. This talk page can be used to talk about improving the article.

small fix to the relativelink fixing script

The script relinks also systemd files pointing to /dev/null. Although this does not break anything currently, here is a fix Copy the following and paste to shell in the directory where the sysroot-relativelinks.py is 

patch <<'EOF'
*** sysroot-relativelinks.py~	Fri Apr 28 09:50:57 2017
--- sysroot-relativelinks.py	Fri Apr 28 10:56:27 2017
***************
*** 18,23 ****
--- 18,25 ----
          return
      if link.startswith(topdir):
          return
+     if link.startswith("/dev/"):
+         return
      #print("Replacing %s with %s for %s" % (link, topdir+link, filep))
      print("Replacing %s with %s for %s" % (link, os.path.relpath(topdir+link, subdir), filep))
      os.unlink(filep)
EOF

Ansible Roles/Playbooks Based on this Article

I used the instructions here to make Ansible playbooks that perform most of the same steps. The playbooks can set up a Pi, set up a development computer, and then deploy Qt to the Pi. Repo is https://bitbucket.org/johnwoltman/build_qt_for_pi_with_ansible

Minor improvement to step 8

You can combine all 5 commands into one like this: 

rsync -avzR pi@raspberrypi.local:/lib :/usr/include :/usr/lib :/opt/vc sysroot

Note that -R preserves the path names and that rsync creates the ./sysroot directory for us.

Hi I have Ubuntu 16.04 x64 and Qt Creator 5.10.1 x64 witch version of qt base should I choose? for compile on raspberry pi 3 with Raspbian stretch x32 OS?

Recommended changes to Step #15

Just including the line: 

  ./qopenglwidget

So that way beginners (like me) know what to do to get it running.

Suggestion of changes to step 14

Make sure you're in "/home/pi" aka "~" when you run these commands:

(This would have saved me an hour...)


Cross compilation on 64bit machines TIP

Hi. When You try to build QT on 64 bit PC without i386 libraries, use: 

  ~/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf-


Recommended changes to Step #4

Honestly, `sudo rpi-update` should only be used by Raspbian developers to the firmware or operating system itself; it pulls from the `next` branch which is usually unstable. At times, it will brick your Raspi.

Please change this to read `sudo apt-get update && sudo apt-get -y upgrade`. This will upgrade the operating system and yes, the firmware as well. It will pull from the stable `master` branch as expected.

error: undefined reference to `__cxa_throw_bad_array_new_length@CXXABI_1.3.8'

When try to build QT Creator app got an error: raspi/sysroot/usr/lib/arm-linux-gnueabihf/libicui18n.so.57:-1: error: undefined reference to `__cxa_throw_bad_array_new_length@CXXABI_1.3.8'

after some exploration add following line to .pro file: QMAKE_LFLAGS += -fuse-ld=gold

Now its ok.

Add section about changed library names

See this (part 6). I cite: "In new Raspbian stretch versions, EGL libraries have different names than those assumed in Qt configuration files, so edit the ./qtbase/mkspecs/devices/linux-rasp-pi*-g++/qmake.conf file and substitute all references to -lEGL and -LGLESv2 for -lbrcmEGL and -lbrcmGLESv2, respectively." (linux-rasp-pi*-g++ refers to the board you're using).

Broken 'link' in Step 5 (part 2)

The qt4-x11 library has depreciated and is no longer available.

Retrieved from "https://wiki.qt.io/index.php?title=Talk:RaspberryPi2EGLFS&oldid=37207"