Qt5.1 on Rasberry Pi (full install not cross-compile)
-
Succes on a Raspberry Pi 2
It took me about 4 hours to configure and compile :)I did change the following: after ./configure and i changed "&> output" to "2>&1 | tee output", this way you can see that something happens
Same with make and I added the -j 4 option to use more processor cores:
make –j 4 2>&1 | tee make_outputTotal configure/build time: 4 hours. The cube application works, but I did not yet manage to make an xwindow application..
-
Succes on a Raspberry Pi 2
It took me about 4 hours to configure and compile :)I did change the following: after ./configure and i changed "&> output" to "2>&1 | tee output", this way you can see that something happens
Same with make and I added the -j 4 option to use more processor cores:
make –j 4 2>&1 | tee make_outputTotal configure/build time: 4 hours. The cube application works, but I did not yet manage to make an xwindow application..
-
@mrelcee
Thanks, after spending a good part of 2 weeks on a version incompatiblilty problem, I finally found this post, downloaded, and installed the .deb file. I am now able to continue porting an application originally written for a Fedora 19 platform. -
Hi,
This stuff is so frustrating for me. I guess I'm out of my league on this stuff.
At any rate , I downloaded and installed the .deb file in this post. That appears to work fine.
Now when I start Qt via a .pro file and attempt to configure Qt versions under build and run I QT reports this:
"The default mkspec syncline is broken". This is after I point "qmake location" to
/usr/local/qt5/bin/qmake.The QT creator version is 2.5.0
What am I doing wrong?
Thanks,
Ron -
@RonL Now that I got this to finally work, I'm having the same issues as you. Any .pro file I attempt to open says No Valid Qt versions found. I point it to Qt 5.5, and it's giving me the error you mentioned. (The default mkspec syncline is broken)
-
Ok,
I started from scratch and downloaded this source version: http://download.qt.io/official_releases/qt/5.4/5.4.1/single/qt-everywhere-opensource-src-5.4.1.tar.gz.mirrorlist .Twenty hours later I now have a working Qt5 environment (of sorts). The make install places Qt5 in the following directory: /usr/local/Qt-5.4.1 . The login PATH environment parameter needs to point to this directory. The PATH also needs to point to /usr/local/Qt-5.4.1/bin if you want to use qmake or any of the other Qt utilities.
I am now able compile an application that needs QT5 with qmake. Although it has a compile time bug that is unrelated to Qt.Now, I down loaded Qt Creator from: http://download.qt.io/official_releases/qtcreator/3.3/3.3.2/qt-creator-opensource-src-3.3.2.tar.gz.mirrorlist. However it will not compile due to an incompatible version of Botan (under /src/libs/3rdparty). If there is a configuration parameter to instruct qmake NOT to include the 3rdparty stuff please let me know.
Thanks,
Ron -
@RonL Did you ever get QtCreator to work properly? If so, how did you do it?
I see other posts where people have installed Arch Linux and they are getting the files from the Arch Arm repository (Qt5.4.1, QtCreator 3.3.1) but I don't want to go that route. I'd rather just download the files I need.
-
Hi,
No not as yet. I have been working with trying to get the Qt 5 libraries build with the features I need for the application that I'm trying to get working. Once that is accomplished I will focus on qtcreator. The whole process has not been pleasant.Thanks,
Ron -
@postmako I tested the Native_Build_of_Qt_5.4.1_on_a_Raspberry_Pi steps as pointed in your wiki.
Any chances you'd have pointers to make it work with PyQt5. I have install PyQt5 (
pip install python-qt5) but I am getting this:pi@raspberrypi ~ $ python Python 2.7.3 (default, Mar 18 2014, 05:13:23) [GCC 4.6.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> from PyQt5 import QtCore, QtGui, QtWebKit Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: cannot import name QtCoreNo sure how to read this message. I'd guessing that it still can't find Qt5 (?)
