Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.

Raspberrypi beginners guide: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
(Redirect to RaspberryPi Beginners Guide)
 
(16 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=Beginner’s guide to cross-compile Qt5 on RaspberryPi=
#REDIRECT [[RaspberryPi Beginners Guide]]


==Introduction==
= Beginner's guide to cross-compile Qt5 on RaspberryPi =


This is a step by step guide to help beginners to: cross-compile QT5 for RaspberryPi(wheezy), create, deploy and run an example project. This article will focus on simplicity, so if you are looking for additional customization, please check a more [[RaspberryPi|detailed guide]] ''[qt.io]''.
== Introduction ==


For an easy install, try [https://gist.github.com/raw/3488286/d1d301946297be999d96df632a0ad0095a4d77e7/bakeqtpi.bash this script.] ''[gist.github.com]''<br /> Or get a later version [http://gitorious.org/bakeqtpi here] ''[gitorious.org]''<br /> For help, run
This is a step by step guide to help beginners to: cross-compile QT5 for RaspberryPi(wheezy), create, deploy and run an example project. This article will focus on simplicity, so if you are looking for additional customization, please check a more [http://wiki.qt.io/RaspberryPi detailed guide].


==Getting Started==
For an easy install, try [https://gist.github.com/raw/3488286/d1d301946297be999d96df632a0ad0095a4d77e7/bakeqtpi.bash this script.]
Or get a later version [http://gitorious.org/bakeqtpi here]
For help, run


First we create a folder to hold the source code and all the required files to do the cross-compilation. We chose to create a directory named “opt” in the home folder:<br />
<code>$ ./bakeqtpi.bash —help</code>


Now, download the following files:
== Getting Started ==


* Raspbian Wheezy image from ([http://www.raspberrypi.org/downloads here] ''[raspberrypi.org]''):<br /> And mount it:<br />
First we create a folder to hold the source code and all the required files to do the cross-compilation. We chose to create a directory named "opt" in the home folder:
<code>paulo@westeros:~$ mkdir~/opt
paulo@westeros:~$ cd~/opt</code>


* The toolchain built by Donald: (Note, seems to be dead links!)<br /> Pro tip: don’t build your own cross-compiler. You’ll overlook something important and loose a couple of hours of your life for nothing. A suitable Raspberry Pi cross-compiler is also available here: https://github.com/raspberrypi/tools
Now, download the following files:
* Raspbian Wheezy image from ([http://www.raspberrypi.org/downloads here]):
<code>paulo@westeros:~/opt$ wget http://downloads.raspberrypi.org/raspbian_latest/ -O wheezy-raspbian-latest.zip
paulo@westeros:~/opt$ unzip wheezy-raspbian-latest.zip</code>
And mount it:
<code>paulo@westeros:~/opt$ sudo mkdir /mnt/rasp-pi-rootfs
paulo@westeros:~/opt$ sudo mount -o loop,offset=62914560 2015-02-16-raspbian-wheezy.img /mnt/rasp-pi-rootfs</code>


It is a 32-bit build so if you are running on a 64-bit machine (you probably are) you need to install ia32-libs:<br />
* The toolchain built by Donald: (Note, seems to be dead links!)
<code>paulo@westeros:~/opt$ wget https://www.dropbox.com/s/sl919ly0q79m1e6/gcc-4.7-linaro-rpi-gnueabihf.tbz
(or a mirror at http://swap.tsmt.eu/gcc-4.7-linaro-rpi-gnueabihf.tbz with sha1 f6255c6aca925239dc943d22a794f642daa17e65)
(or better at http://de.sourceforge.jp/projects/sfnet_rfidmonitor/downloads/crosscompilation-resources/gcc-4.7-linaro-rpi-gnueabihf.tbz
as the above noted links seem to be broken)
paulo@westeros:~/opt$ tar -xf gcc-4.7-linaro-rpi-gnueabihf.tbz</code>
Pro tip: don't build your own cross-compiler. You'll overlook something important and loose a couple of hours of your life for nothing. A suitable Raspberry Pi cross-compiler is also available here: https://github.com/raspberrypi/tools


* Clone the cross-compile-tools repository:<br />
It is a 32-bit build so if you are running on a 64-bit machine (you probably are) you need to install ia32-libs:
<code>paulo@westeros:~/opt$ sudo apt-get install ia32-libs</code>


* Clone and init the Qt5 repository:<br /> If you’re behind a firewall ./init-repository might fail. First run this command:<br /> Then retry:<br />
* Clone the cross-compile-tools repository:
<code>paulo@westeros:~/opt$ git clone git://gitorious.org/cross-compile-tools/cross-compile-tools.git</code>


* Finally, apply a patch on the qtjsbackend repository:<br />
* Clone and init the Qt5 repository:
<code>paulo@westeros:~/opt$ git clone git://gitorious.org/qt/qt5.git
paulo@westeros:~/opt$ cd qt5
paulo@westeros:~/opt/qt5$ ./init-repository</code>
If you're behind a firewall ./init-repository might fail. First run this command:
<code>paulo@westeros:~/opt/qt5$ sed -i 's/git:/https:git./' .gitmodules</code>
Then retry:
<code>paulo@westeros:~/opt/qt5$ ./init-repository -f</code>


==Compiling qtbase==
* Finally, apply a patch on the qtjsbackend repository (Nb: You shouldn't need to patch with the latest verson of the Qt5 repo):
<code>paulo@wseteros:~/opt/qt5$ cd ~/opt/qt5/qtjsbackend
paulo@wseteros:~/opt/qt5/qtjsbackend$ git fetch https://codereview.qt.io/p/qt/qtjsbackend refs/changes/56/27256/4 && git cherry-pick FETCH_HEAD</code>


== Compiling qtbase ==
Now the we have all the resources needed to compile qt5 for raspberry, we need to execute a script to fix symlinks and lib paths:
Now the we have all the resources needed to compile qt5 for raspberry, we need to execute a script to fix symlinks and lib paths:


Go to the qt5/qtbase folder and run:<br /> Note: if you want the qmlscene binary you should add -make tools to the ./configure command.
<code>paulo@westeros:~$ cd~/opt/cross-compile-tools
paulo@westeros:~$ sudo ./fixQualifiedLibraryPaths /mnt/rasp-pi-rootfs/ ~/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-gcc</code>


==Compiling other modules==
Go to the qt5/qtbase folder and run:
<code>paulo@westeros:~/opt/qt5/qtbase$ ./configure -opengl es2 -device linux-rasp-pi-g++ -device-option CROSS_COMPILE=~/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf- -sysroot /mnt/rasp-pi-rootfs -opensource -confirm-license -optimized-qmake -reduce-exports -release -make libs -prefix /usr/local/qt5pi
paulo@westeros:~/opt/qt5/qtbase$ make -j 4
paulo@westeros:~/opt/qt5/qtbase$ sudo make install</code>
Note: if you want the qmlscene binary you should add -make tools to the ./configure command.


Now that you have qmake, you can cross-compile the other modules. To avoid dependencies errors, the following order is sugested:<br /> qtimageformats, qtsvg, qtjsbackend, qtscript, qtxmlpatterns, qtdeclarative, qtsensors, qt3d, qtgraphicaleffects, qtjsondb, qtlocation, qtdocgallery.
== Compiling other modules ==


To compile, you must do like the example below:<br />
Now that you have qmake, you can cross-compile the other modules. To avoid dependencies errors, the following order is sugested:
qtimageformats, qtsvg, qtjsbackend, qtscript, qtxmlpatterns, qtdeclarative, qtsensors, qt3d, qtgraphicaleffects, qtjsondb, qtlocation, qtdocgallery.


We have all the modules installed in the wheezy image, now we can copy it to the sdcard using dd:<br />
To compile, you must do like the example below:
<code>paulo@westeros:~/opt/qt5$ cd qtimageformats
paulo@westeros:~/opt/qt5/qtimageformats$ /usr/local/qt5pi/bin/qmake .
paulo@westeros:~/opt/qt5/qtimageformats$ make -j4
paulo@westeros:~/opt/qt5/qtimageformats$ sudo make install</code>
 
We have all the modules installed in the wheezy image, now we can copy it to the sdcard using dd:
<code>paulo@westeros:~/opt/qt5$ cd~/opt/
paulo@westeros:~/opt$ sync; sudo umount /mnt/rasp-pi-rootfs
paulo@westeros:~/opt$ sudo dd bs=1M if=2015-02-16-raspbian-wheezy.img of=/dev/sdb; sync
</code>


obs: Check the entry point of your sdcard. Mine was /dev/sdb.
obs: Check the entry point of your sdcard. Mine was /dev/sdb.


'''Notes for <span class="caps">OSX</span>'''
'''Notes for OSX'''


* Because your sdcard will be partitioned, <span class="caps">OSX</span> won’t let you umount it, so you’ll need to type: <br />
* Because your sdcard will be partitioned, OSX won't let you umount it, so you'll need to type:
<code>sudo diskutil umountDisk /dev/disk3</code>


where “disk3” will be the /dev/diskXsY where your sdcard first appeared.
where "disk3" will be the /dev/diskXsY where your sdcard first appeared.


* To perform dd you will need to use the *r*disk index, so if your sdcard is disk3 you will need to type:<br />
* To perform dd you will need to use the *r*disk index, so if your sdcard is disk3 you will need to type:
<code>sudo dd bs=1M if=2015-02-16-wheezy-raspbian.img of=/dev/rdisk3; sync</code>


Boot up your pi.
Boot up your pi.


==Configuring Qt Creator==
== Configuring Qt Creator ==


To use Qt Creator properly, you must configure the “Qt Version” and “Tool Chains” sections.
To use Qt Creator properly, you must configure the "Qt Version" and "Tool Chains" sections.


===Tool Chain Settings===
=== Tool Chain Settings ===


go to '''Tools -&gt; Options.. -&gt; Build &amp; Run -&gt; Compilers''' tab.<br /> click in '''Add -&gt; <span class="caps">GCC</span>'''.<br /> On '''Compiler Path'''set to /home/&lt;you&gt;/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-g++”.<br /> Name it “<span class="caps">ARM</span> <span class="caps">GCC</span>” or similar.<br /> obs: Adjust it to your username.
go to '''Tools -> Options..-> Build & Run -> Compilers''' tab.
click in "'''Add -> GCC'''".
On "'''Compiler Path'''" set to "/home/<you>/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-g+''".
Name it "ARM GCC" or similar.
obs: Adjust it to your username.


===Qt Version settings.===
=== Qt Version settings. ===
Now go to '''Tools -> Options..-> Build & Run -> Qt Versions''' tab.
Click in "Add.." and choose you qmake for raspberry "/usr/local/qt5pi/bin/qmake".


Now go to '''Tools -&gt; Options.. -&gt; Build &amp; Run -&gt; Qt Versions''' tab.<br /> Click in “Add..” and choose you qmake for raspberry “/usr/local/qt5pi/bin/qmake”.
'''Note for OSX'''
* Because /usr is not visible by default, you first need to open a terminal and type:
<code>sudo SetFile -a v /usr</code>
* After you've completed the qmake selection, if you wish to make /usr invisible again, type the same command with a capital V :
<code>sudo SetFile -a V /usr</code>


'''Note for <span class="caps">OSX</span>'''
=== Configure Linux Devices ===
Go to '''Tools -> Options…-> Devices -> Devices''' tab.


* Because /usr is not visible by default, you first need to open a terminal and type:<br />
Add a new configuration setting a "Generic Linux Device"
* After you’ve completed the qmake selection, if you wish to make /usr invisible again, type the same command with a capital V :<br />
Hostname or IP address is the IP of your raspberry
 
user is '''pi'''
===Configure Linux Devices===
password is '''raspberry'''
 
obs: if your not did change it.
Go to '''Tools -&gt; Options… -&gt; Devices -&gt; Devices''' tab.
 
Add a new configuration setting a “Generic Linux Device”<br /> Hostname or IP address is the IP of your raspberry<br /> user is '''pi'''<br /> password is '''raspberry'''<br /> obs: if your not did change it.


Now you are ready to run your first Qt raspberry pi project.
Now you are ready to run your first Qt raspberry pi project.


==Example Project==
== Example Project ==
 
You can download a hello world project:
You can download a hello world project:<br />
<code>paulo@westeros:~$ git clone https://git.gitorious.org/qt5-raspberrypi-example/qt5-raspberrypi-example.git</code>


Open the project in Qt Creator and go to the Projects pane.<br /> Click Manage Kits and then Add.<br /> Fill in:<br /> Name: Raspberry Pi<br /> Device Type: Generic Linux Device<br /> Device: Raspberry Pi<br /> Compiler: <span class="caps">ARM</span> <span class="caps">GCC</span><br /> Debugger-&gt;Manage-&gt;Edit-&gt;”/home/&lt;you&gt;/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-gdb” (change your username)<br /> Qt version: Qt 5.x.x (qt5pi)<br /> Ok-&gt;Add Kit-&gt;Raspberry Pi
Open the project in Qt Creator and go to the Projects pane.
Click Manage Kits and then Add.
Fill in:
Name: Raspberry Pi
Device Type: Generic Linux Device
Device: Raspberry Pi
Compiler: ARM GCC
Debugger->Manage->Edit->"/home/<you>/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-gdb" (change your username)
Qt version: Qt 5.x.x (qt5pi)
Ok->Add Kit->Raspberry Pi


Then go to the “Rasperry Pi” kit tab-&gt;System Environment and add LD_LIBRARY_PATH which is set to /usr/local/qt5pi/lib
Then go to the "Rasperry Pi" kit tab->System Environment and add LD_LIBRARY_PATH which is set to /usr/local/qt5pi/lib


Now you can build and run your application from Qt Creator.
Now you can build and run your application from Qt Creator.


==Troubleshooting==
== Troubleshooting ==
=== Qt version not properly installed ===
You need to keep the SD card image mounted during development!


===Qt version not properly installed===
If QtCreator still reports this after mounting the SD card image, then you may need to create the directories missing from


You need to keep the SD card image mounted during development!
<code>/mnt/rasp-pi-rootfs/usr/local/qt5pi/</code>
 
If QtCreator still reports this after mounting the SD card image, then you may need to create the directories missing from


or whatever the mount path is (these will probably include bin, translations, and so on). You can create empty directories using the mkdir command.
or whatever the mount path is (these will probably include bin, translations, and so on). You can create empty directories using the mkdir command.


===The default mkspec symlink is broken.===
=== The default mkspec symlink is broken. ===
It means that mkspec is not found on your sysroot, so your must copy it.


It means that mkspec is not found on your sysroot, so your must copy it.
<code>paulo@westeros:~$ sudo cp -r /usr/local/qt5pi/mkspecs/ /mnt/rasp-pi-rootfs/usr/local/qt5pi/</code>


If the problem persists, create the missing symlink, e.g.
If the problem persists, create the missing symlink, e.g.
<code>sudo ln -s /usr/local/qt5pi/mkspecs/devices/linux-rasp-pi-g''+ /usr/local/qt5pi/mkspecs/default</code>


It is probably a good idea to do the same for the sysroot mkspecs.
It is probably a good idea to do the same for the sysroot mkspecs.


===Include &lt;QtGui/QtGui&gt;: No such file or directory===
=== Include <QtGui/QtGui>: No such file or directory ===


It seems Qt’s include was not found and you must add it to you .pro file:
It seems Qt's include was not found and you must add it to you .pro file:


===cc1: fatal error: .pch/release-shared/QtGui: No such file or directory===
<code>INCLUDEPATH ''= /mnt/rasp-pi-rootfs/usr/local/qt5pi/include/</code>


Some people have seen this error. Adding the -no-pch” option when running configure should prevent it.
=== cc1: fatal error: .pch/release-shared/QtGui: No such file or directory ===
Some people have seen this error. Adding the "-no-pch" option when running configure should prevent it.


===Getting Could not determine the target architecture! and Could not determine the host architecture!===
=== Getting Could not determine the target architecture! and Could not determine the host architecture! ===
If you are getting this kind of error, it is possible that your current git branch is something other than master. To be sure, do the following:


If you are getting this kind of error, it is possible that your current git branch is something other than master. To be sure, do the following:
<code>daniel@daniel-t3500 : ~/opt/qt5/qtbase $ git branch </code>


If it shows like this:<br />
If it shows like this:
<code>* (no branch)
master</code>


Then you must checkout to master branch before running ./configure:<br />
Then you must checkout to master branch before running ./configure:
<code>daniel@daniel-t3500 :~/opt/qt5/qtbase $ git checkout master
daniel@daniel-t3500 : ~/opt/qt5/qtbase $ git branch
* master</code>


It is also good to fetch the latest commits and apply them by doing:<br />
It is also good to fetch the latest commits and apply them by doing:
<code>daniel@daniel-t3500 :~/opt/qt5/qtbase $ git pull</code>


Also, check for the installation of libz (32 bits) in yor system. In ubuntu (64 bits) you might just:<br />
Also, check for the installation of libz (32 bits) in yor system. In ubuntu (64 bits) you might just:
<code>sudo apt-get install lib32z1-dev</code>


After the ./configure script has failed first run these commands before restarting ./configure:
After the ./configure script has failed first run these commands before restarting ./configure:


===<span class="caps">EGL</span> Error : Could not create the egl surface: error = 0×3000===
<code>daniel@daniel-t3500 : ~/opt/qt5/qtbase $ git reset —hard
daniel@daniel-t3500 :~/opt/qt5/qtbase $ git git clean -dxf</code>


=== EGL Error : Could not create the egl surface: error = 0x3000 ===
Try allocating more memory to video (try 64 or 128MB). Use the raspi-config utility to change this.
Try allocating more memory to video (try 64 or 128MB). Use the raspi-config utility to change this.


===<span class="caps">ABI</span> detection failed===
<code>pi@raspberrypi ~ $ sudo raspi-config</code>
 
You will need Qt Creator 2.6 for Qt5 up to and including beta2.<br /> Any Qt 5 later than that will need to use nightly snapshots (or will have to wait for Qt Creator 2.6.1): After the beta2 all libraries were renamed again.
 
See [http://forum.qt.io/viewthread/22023 this forum thread for more details] ''[qt.io]''


===./configure: 2654: ./configure: /home/&lt;you&gt;/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-g++: not found -reduce-exports was requested but this compiler does not support it===
=== ABI detection failed ===
You will need Qt Creator 2.6 for Qt5 up to and including beta2.
Any Qt 5 later than that will need to use nightly snapshots (or will have to wait for Qt Creator 2.6.1): After the beta2 all libraries were renamed again.


The error message is totally misleading. The real cause is that the precompile toolchain is 32-bit, so you need to:<br />
See [http://forum.qt.io/viewthread/22023 this forum thread for more details]


===make: g++: Command not found===
=== ./configure: 2654: ./configure: /home/<you>/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-g: not found -reduce-exports was requested but this compiler does not support it ===
The error message is totally misleading. The real cause is that the precompile toolchain is 32-bit, so you need to:
<code>sudo apt-get install ia32-libs</code>


Qt requires a native (non-cross-compiling) copy of g++ to be installed in order to build qmake. You can’t use clang. Fix with:<br />
=== make: g: Command not found ===
Qt requires a native (non-cross-compiling) copy of g''+ to be installed in order to build qmake. You can't use clang. Fix with:
<code>sudo apt-get install g++</code>


===/mnt/rasp-pi-rootfs/usr/lib/arm-linux-gnueabihf/libdl.a(dlopen.o): In function `dlopen’: (.text+0xc): undefined reference to `__dlopen’===
=== /mnt/rasp-pi-rootfs/usr/lib/arm-linux-gnueabihf/libdl.a(dlopen.o): In function `dlopen': (.text+0xc): undefined reference to `__dlopen' ===


You need to run the ./fixQualifiedLibraryPaths again.
You need to run the ./fixQualifiedLibraryPaths again.
Line 150: Line 229:
See: http://stackoverflow.com/questions/13626726/an-error-building-qt-libraries-for-the-raspberry-pi for more info.
See: http://stackoverflow.com/questions/13626726/an-error-building-qt-libraries-for-the-raspberry-pi for more info.


===cc1: fatal error: .pch/release-shared/Qt5Gui: No such file or directory===
=== cc1: fatal error: .pch/release-shared/Qt5Gui: No such file or directory ===


Try adding -no-pch to the ./configure command line.
Try adding -no-pch to the ./configure command line.


===Cannot create forwarding script Betrete ‘qtactiveqt’.git/hooks/commit-msg: Datei oder Verzeichnis nicht gefunden===
=== Cannot create forwarding script Betrete 'qtactiveqt'.git/hooks/commit-msg: Datei oder Verzeichnis nicht gefunden ===


Try:<br />
Try:
<code>unset LANG
./init-repository -f</code>

Latest revision as of 08:28, 9 April 2015

Beginner's guide to cross-compile Qt5 on RaspberryPi

Introduction

This is a step by step guide to help beginners to: cross-compile QT5 for RaspberryPi(wheezy), create, deploy and run an example project. This article will focus on simplicity, so if you are looking for additional customization, please check a more detailed guide.

For an easy install, try this script. Or get a later version here For help, run

$ ./bakeqtpi.bash help

Getting Started

First we create a folder to hold the source code and all the required files to do the cross-compilation. We chose to create a directory named "opt" in the home folder:

paulo@westeros:~$ mkdir~/opt
paulo@westeros:~$ cd~/opt

Now, download the following files:

  • Raspbian Wheezy image from (here):
paulo@westeros:~/opt$ wget http://downloads.raspberrypi.org/raspbian_latest/ -O wheezy-raspbian-latest.zip
paulo@westeros:~/opt$ unzip wheezy-raspbian-latest.zip

And mount it:

paulo@westeros:~/opt$ sudo mkdir /mnt/rasp-pi-rootfs
paulo@westeros:~/opt$ sudo mount -o loop,offset=62914560 2015-02-16-raspbian-wheezy.img /mnt/rasp-pi-rootfs
  • The toolchain built by Donald: (Note, seems to be dead links!)
paulo@westeros:~/opt$ wget https://www.dropbox.com/s/sl919ly0q79m1e6/gcc-4.7-linaro-rpi-gnueabihf.tbz
(or a mirror at http://swap.tsmt.eu/gcc-4.7-linaro-rpi-gnueabihf.tbz with sha1 f6255c6aca925239dc943d22a794f642daa17e65)
(or better at http://de.sourceforge.jp/projects/sfnet_rfidmonitor/downloads/crosscompilation-resources/gcc-4.7-linaro-rpi-gnueabihf.tbz
as the above noted links seem to be broken)
paulo@westeros:~/opt$ tar -xf gcc-4.7-linaro-rpi-gnueabihf.tbz

Pro tip: don't build your own cross-compiler. You'll overlook something important and loose a couple of hours of your life for nothing. A suitable Raspberry Pi cross-compiler is also available here: https://github.com/raspberrypi/tools

It is a 32-bit build so if you are running on a 64-bit machine (you probably are) you need to install ia32-libs:

paulo@westeros:~/opt$ sudo apt-get install ia32-libs
  • Clone the cross-compile-tools repository:
paulo@westeros:~/opt$ git clone git://gitorious.org/cross-compile-tools/cross-compile-tools.git
  • Clone and init the Qt5 repository:
paulo@westeros:~/opt$ git clone git://gitorious.org/qt/qt5.git
paulo@westeros:~/opt$ cd qt5
paulo@westeros:~/opt/qt5$ ./init-repository

If you're behind a firewall ./init-repository might fail. First run this command:

paulo@westeros:~/opt/qt5$ sed -i 's/git:/https:git./' .gitmodules

Then retry:

paulo@westeros:~/opt/qt5$ ./init-repository -f
  • Finally, apply a patch on the qtjsbackend repository (Nb: You shouldn't need to patch with the latest verson of the Qt5 repo):
paulo@wseteros:~/opt/qt5$ cd ~/opt/qt5/qtjsbackend
paulo@wseteros:~/opt/qt5/qtjsbackend$ git fetch https://codereview.qt.io/p/qt/qtjsbackend refs/changes/56/27256/4 && git cherry-pick FETCH_HEAD

Compiling qtbase

Now the we have all the resources needed to compile qt5 for raspberry, we need to execute a script to fix symlinks and lib paths:

paulo@westeros:~$ cd~/opt/cross-compile-tools
paulo@westeros:~$ sudo ./fixQualifiedLibraryPaths /mnt/rasp-pi-rootfs/ ~/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-gcc

Go to the qt5/qtbase folder and run:

paulo@westeros:~/opt/qt5/qtbase$ ./configure -opengl es2 -device linux-rasp-pi-g++ -device-option CROSS_COMPILE=~/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf- -sysroot /mnt/rasp-pi-rootfs -opensource -confirm-license -optimized-qmake -reduce-exports -release -make libs -prefix /usr/local/qt5pi
paulo@westeros:~/opt/qt5/qtbase$ make -j 4
paulo@westeros:~/opt/qt5/qtbase$ sudo make install

Note: if you want the qmlscene binary you should add -make tools to the ./configure command.

Compiling other modules

Now that you have qmake, you can cross-compile the other modules. To avoid dependencies errors, the following order is sugested: qtimageformats, qtsvg, qtjsbackend, qtscript, qtxmlpatterns, qtdeclarative, qtsensors, qt3d, qtgraphicaleffects, qtjsondb, qtlocation, qtdocgallery.

To compile, you must do like the example below:

paulo@westeros:~/opt/qt5$ cd qtimageformats
paulo@westeros:~/opt/qt5/qtimageformats$ /usr/local/qt5pi/bin/qmake .
paulo@westeros:~/opt/qt5/qtimageformats$ make -j4
paulo@westeros:~/opt/qt5/qtimageformats$ sudo make install

We have all the modules installed in the wheezy image, now we can copy it to the sdcard using dd:

paulo@westeros:~/opt/qt5$ cd~/opt/
paulo@westeros:~/opt$ sync; sudo umount /mnt/rasp-pi-rootfs
paulo@westeros:~/opt$ sudo dd bs=1M if=2015-02-16-raspbian-wheezy.img of=/dev/sdb; sync

obs: Check the entry point of your sdcard. Mine was /dev/sdb.

Notes for OSX

  • Because your sdcard will be partitioned, OSX won't let you umount it, so you'll need to type:
sudo diskutil umountDisk /dev/disk3

where "disk3" will be the /dev/diskXsY where your sdcard first appeared.

  • To perform dd you will need to use the *r*disk index, so if your sdcard is disk3 you will need to type:
sudo dd bs=1M if=2015-02-16-wheezy-raspbian.img of=/dev/rdisk3; sync

Boot up your pi.

Configuring Qt Creator

To use Qt Creator properly, you must configure the "Qt Version" and "Tool Chains" sections.

Tool Chain Settings

go to Tools -> Options..-> Build & Run -> Compilers tab. click in "Add -> GCC". On "Compiler Path" set to "/home/<you>/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-g+". Name it "ARM GCC" or similar. obs: Adjust it to your username.

Qt Version settings.

Now go to Tools -> Options..-> Build & Run -> Qt Versions tab. Click in "Add.." and choose you qmake for raspberry "/usr/local/qt5pi/bin/qmake".

Note for OSX

  • Because /usr is not visible by default, you first need to open a terminal and type:
sudo SetFile -a v /usr
  • After you've completed the qmake selection, if you wish to make /usr invisible again, type the same command with a capital V :
sudo SetFile -a V /usr

Configure Linux Devices

Go to Tools -> Options…-> Devices -> Devices tab.

Add a new configuration setting a "Generic Linux Device" Hostname or IP address is the IP of your raspberry user is pi password is raspberry obs: if your not did change it.

Now you are ready to run your first Qt raspberry pi project.

Example Project

You can download a hello world project:

paulo@westeros:~$ git clone https://git.gitorious.org/qt5-raspberrypi-example/qt5-raspberrypi-example.git

Open the project in Qt Creator and go to the Projects pane. Click Manage Kits and then Add. Fill in: Name: Raspberry Pi Device Type: Generic Linux Device Device: Raspberry Pi Compiler: ARM GCC Debugger->Manage->Edit->"/home/<you>/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-gdb" (change your username) Qt version: Qt 5.x.x (qt5pi) Ok->Add Kit->Raspberry Pi

Then go to the "Rasperry Pi" kit tab->System Environment and add LD_LIBRARY_PATH which is set to /usr/local/qt5pi/lib

Now you can build and run your application from Qt Creator.

Troubleshooting

Qt version not properly installed

You need to keep the SD card image mounted during development!

If QtCreator still reports this after mounting the SD card image, then you may need to create the directories missing from

/mnt/rasp-pi-rootfs/usr/local/qt5pi/

or whatever the mount path is (these will probably include bin, translations, and so on). You can create empty directories using the mkdir command.

The default mkspec symlink is broken.

It means that mkspec is not found on your sysroot, so your must copy it.

paulo@westeros:~$ sudo cp -r /usr/local/qt5pi/mkspecs/ /mnt/rasp-pi-rootfs/usr/local/qt5pi/

If the problem persists, create the missing symlink, e.g.

sudo ln -s /usr/local/qt5pi/mkspecs/devices/linux-rasp-pi-g''+ /usr/local/qt5pi/mkspecs/default

It is probably a good idea to do the same for the sysroot mkspecs.

Include <QtGui/QtGui>: No such file or directory

It seems Qt's include was not found and you must add it to you .pro file:

INCLUDEPATH ''= /mnt/rasp-pi-rootfs/usr/local/qt5pi/include/

cc1: fatal error: .pch/release-shared/QtGui: No such file or directory

Some people have seen this error. Adding the "-no-pch" option when running configure should prevent it.

Getting Could not determine the target architecture! and Could not determine the host architecture!

If you are getting this kind of error, it is possible that your current git branch is something other than master. To be sure, do the following:

daniel@daniel-t3500 : ~/opt/qt5/qtbase $ git branch

If it shows like this:

* (no branch)
 master

Then you must checkout to master branch before running ./configure:

daniel@daniel-t3500 :~/opt/qt5/qtbase $ git checkout master
daniel@daniel-t3500 : ~/opt/qt5/qtbase $ git branch
* master

It is also good to fetch the latest commits and apply them by doing:

daniel@daniel-t3500 :~/opt/qt5/qtbase $ git pull

Also, check for the installation of libz (32 bits) in yor system. In ubuntu (64 bits) you might just:

sudo apt-get install lib32z1-dev

After the ./configure script has failed first run these commands before restarting ./configure:

daniel@daniel-t3500 : ~/opt/qt5/qtbase $ git reset hard
daniel@daniel-t3500 :~/opt/qt5/qtbase $ git git clean -dxf

EGL Error : Could not create the egl surface: error = 0x3000

Try allocating more memory to video (try 64 or 128MB). Use the raspi-config utility to change this.

pi@raspberrypi ~ $ sudo raspi-config

ABI detection failed

You will need Qt Creator 2.6 for Qt5 up to and including beta2. Any Qt 5 later than that will need to use nightly snapshots (or will have to wait for Qt Creator 2.6.1): After the beta2 all libraries were renamed again.

See this forum thread for more details

./configure: 2654: ./configure: /home/<you>/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-g: not found -reduce-exports was requested but this compiler does not support it

The error message is totally misleading. The real cause is that the precompile toolchain is 32-bit, so you need to:

sudo apt-get install ia32-libs

make: g: Command not found

Qt requires a native (non-cross-compiling) copy of g+ to be installed in order to build qmake. You can't use clang. Fix with:

sudo apt-get install g++

/mnt/rasp-pi-rootfs/usr/lib/arm-linux-gnueabihf/libdl.a(dlopen.o): In function `dlopen': (.text+0xc): undefined reference to `__dlopen'

You need to run the ./fixQualifiedLibraryPaths again.

See: http://stackoverflow.com/questions/13626726/an-error-building-qt-libraries-for-the-raspberry-pi for more info.

cc1: fatal error: .pch/release-shared/Qt5Gui: No such file or directory

Try adding -no-pch to the ./configure command line.

Cannot create forwarding script Betrete 'qtactiveqt'.git/hooks/commit-msg: Datei oder Verzeichnis nicht gefunden

Try:

unset LANG
./init-repository -f