Qt5.1 on Rasberry Pi (full install not cross-compile)

RodriguesCunha

I tried what you did but i get a different error:

Project ERROR: Unknown module(s) in QT: script

postmako

Not sure on those unknown module errors. I'll have to look at them when I get more time.

Regarding the closing the app, if you are in the console Ctrl+Alt+Backspace works, Ctrl+C might work as well. In x-windows, I haven't figured out which key combo works but in your app you can add a this->close(); in the main window class wherever appropriate.

RodriguesCunha

I'm now trying to compile and install qtscript module and after if i get your error i will do the same with qttools (it seems to be related to designer).

postmako

Yeah I was pretty sure mine compiled qttools because the .obj directory is populated (FYI - In Linux anytime a file or directory starts with a period (.), the file or directory will be hidden), but it still complains about designer. I ran qmake without the -r and then I'm running make now. Quite an experiment from two rather inexperienced Qt bit diddlers eh? I'm a software engineer by trade but this is the first time I've used Qt.

dawuss

Hi!
I am currently compiling qt as written in the wiki, but I had to leave the configuration file vanilla. When I applied the changes the configure script stopped telling me something about an unterminated string.
I hope the compilation will be finished on monday :o)
I also would like to use qt designer, so i somebody knows how to compile it I would be happy!

postmako

Just an FYI, if you don't manually make the changes to the configure script then it will not build PulseAudio, DBus, or some of the others.

RodriguesCunha

Hi postmako.

Did you had any luck on Qtcreator?
Mine first complainned about: unknown module: script.
I build and installed qtscript module. This error resolved.
Next try i got unknown module:declarative.
I build and installed qtdeclarative module and also qttools, but i still get unknown module: declarative.

As i can see it will be necessary to build and install some other modules...
The problem is that it's complainning about declarative but i already build and installed it...

Any ideas?

postmako

Sorry no, I need to learn more about this before getting any further as well.

RodriguesCunha

The only info i found on the web states that declarative module was renamed to quick, but this was on Qtcreator 2.6....

dawuss

[quote author="postmako" date="1375481184"]Just an FYI, if you don't manually make the changes to the configure script then it will not build PulseAudio, DBus, or some of the others.[/quote]

THX for the hint. Somehow changing the file manually did not work, using the patch file didn´t work either:

pi@raspberrypi ~/opt/qt5 $ patch -p0 < raspberry.patch
patch: **** Only garbage was found in the patch input.

Same when putting the patch file into the qtbase dir and calling patch there. I have no idea what the problem is.

It would be nice if the patch file could be downloaded and the right "patch" command would be given. I used patches on the linux kernel 1000 times, but seems I an unable to get this little thing working here. :-/

postmako

Click on my profile and send me your configure script, I'll try to see why yours is different.

RodriguesCunha

Hi postmako.
I still didn't managed to build Qtcreator.
After build and install qtquick1 module the declarative error was resolved. But now i get the same you had: designercomponents designer.

One other thing, is it possible when building an app, define it not to use opengl?

My problem is that i want to show my app (running on RPi) on my laptop (not on monitor), using x11vnc and tightvncviewer. I get the same screen as pi, but i can't get the hdmi output because of opengl.
Is there any way to do it, or should i build again Qt and in configure do not use -opengl es2?

Thanks

postmako

As far as I know adding the -opengl es2 to the configure is just telling Qt to configure opengl for ES2 not the desktop. It should not matter when it comes to building your apps. There is probably something wrong with your application.

Did you try building the sample apps in /home/pi/opt/qt5/qtbase/examples/ ?

RodriguesCunha

Hi,
I tried to build some examples, but i get the same.
On my laptop i get everything but the app.
When i plug the hdmi monitor, the app is showing.
So i don't know if the problem is on RPi or on Qt side...
I read that it's not possible to get same screen on monitor and laptop if it's using opengl.
Like i said, on RPi i'm using x11vnc and on laptop tightvncviewer.

If you want, i can send you my app code. But i think the problem it's not in my app. My app is working well in Ubuntu and on Windows 7.
One thing different is that in RPi, when i start app it's always fullscreen, but in the other OS it's not and so i get the buttons to maximize, minimize and close.

Thanks

postmako

Are you running the app in x-windows or from the terminal?

RodriguesCunha

From terminal, inside x-windows.

postmako

Maybe this is helpful: "http://qt-project.org/forums/viewthread/22903":http://qt-project.org/forums/viewthread/22903

It basically says "it will be fullscreen if you are using the eglfs QPA plugin"

Then I found this: "http://qt-project.org/forums/viewthread/10466":http://qt-project.org/forums/viewthread/10466

I noticed this in the qmake.conf file:
@QT_QPA_DEFAULT_PLATFORM = wayland@

So you could change that to xcb and rebuild or you could build and install wayland and get that to work. But when I typed ./app_name -platform xcb it worked in a window.

Interesting, I guess it is good to learn something new everyday...

Let me know what you end up doing, I'm still learning too.

postmako

I also came across these for wayland support: "http://wayland.freedesktop.org/raspberrypi.html":http://wayland.freedesktop.org/raspberrypi.html

Then build similar to these instructions: "http://qt-project.org/wiki/QtWayland":http://qt-project.org/wiki/QtWayland

@WLD=$HOME/Apps/Wayland # change this to another location if you prefer
LD_LIBRARY_PATH=$WLD/lib
PKG_CONFIG_PATH=$WLD/lib/pkgconfig/:$WLD/share/pkgconfig/
ACLOCAL="aclocal -I $WLD/share/aclocal"
PATH=$WLD/bin:$PATH
XDG_RUNTIME_DIR=/tmp

export WLD LD_LIBRARY_PATH PKG_CONFIG_PATH ACLOCAL PATH XDG_RUNTIME_DIR

git clone git://gitorious.org/qt/qtwayland.git
cd qtwayland
qmake
make
make install@

RodriguesCunha

Hi postmako
Using your suggestion ./app_name -platform xcb now i get the window and it works over vnc.
Thanks

geoffml

Hi,
At last I have found a link that actually works, thanks guys. I am running the cube example on my Pi. Now I want to run a working Qt5 Windows 32 bit app on my Pi. Has anybody done this yet with Qt5? As it is suggested, can I place all the associated files on my Pi and compile the .pro project and run qmake etc or is this too simplistic?
Just a few points to make compilation a little quicker. It took me 30 hours to compile

Reduce memory share to 16
Do not enable SSH
Overclocked at MEDIUM level only. Could be quicker if TURBO used.

Note to run the cube example return the memory share to at least 128 otherwise nothing happens on the screen. CTRL+ALT+BACKSPACE to exit.
Thanks