QtonPi

My pleasure.

I was reading all pi stuff I can find anyway.

QGLview is now a subclass of Qwindow not Qwidget.

Just change the constructor argument to:
@TeapotView(QWindow *parent = 0)@

And you should be good to go.

The documentation for QT3D is atrocious now'a'days.

But you can checkout updated examples directly from the git repos.

http://qt.gitorious.org/qt/qt3d/trees/master/examples/qt3d/teapot

Updated the swap file to 8GB, and it's seems OK for now, but the build is very very slow.

I'm having fun with wayland... nothing released yet , but I plan to port my existing app to qt5 once it's stable ...

once qt5-rc1 is finished to be rebuilt on rpi (yes through NFS) ...

--
http://rzr.online.fr/q/wayland# tested #WayLand 's #Weston Terminal , building #Qt5 rc1 on #RaspBian , ask me to share #RaspberryPi 's bins.

I managed to fix this by choosing a correct sysroot. The one it was pointing at had a broken symlink, which caused the library to fail

I managed to install qt50-snapshot when I used "deb http://archive.qmh-project.org/rpi-wheezy/debian unstable main" line in /etc/apt/sources.list. I didn't get my cross-compile environment to work though. My Qt creator doesn't found target device after I installed qt50-snapshot.

Thank you for the hint. I have unmounted the raspbian image before I tried to configure the Qt Verions. Remounting the image solves the problem and now it works as expected.

Hello, I don't know whether this thread is active or not so simply try. I have used the bakeqtpi.bash script from http://qt-project.org/wiki/RaspberryPi_Beginners_guide. At the end I got the following messages:

Compiled qtimageformats
Compiled qtsvg
Compiled qtjsbackend
Compiled qtscript
Compiled qtxmlpatterns
Compiled qtdeclarative
Failed qtsensors
Failed qt3d
Compiled qtgraphicaleffects
Failed qtjsondb
Failed qtlocation
Compiled qtquick1
Failed qtsystems
Compiled qtmultimedia

What exactly does this mean to me? Will QT5 run properly on my PI?

thanks for your feedback

I have the same issue, but not with rasperian :-( I have the 512Mb version, I'm thinking that is the issue ?????

Has anybody got it working on RPi 512Mb??

Thanks for your help. I was able to solve this "myself" though, but had not yet posted the answer here.

The problem was not with the libraries for the target, but for the host. I had it installed on a 64-bit machine, and the libraries had to be 32 bit. It compiled fine after I installed the i686 versions of libz-devel and libmpc-devel.

There was something funny with the libz though. The compiler gave me errors, saying that it could not get the version information for zlib, unable to find the absolute file location. I was able to ls -l it though. It showed a symlink pointing from libz.so.1 to libz.so.1.x.x (I don't remember the exact version). I deleted and recreated this symlink, and it was fixed.

Now I just have to get qt working on the pi...

@jcverdie

I followed the beginners guide like yourself also and ran into the same problem.

Apps deployed and executed from within QtCreator ran correctly on the device but if I went to the command line on the RPi itself, I couldn't execute them (libQtQuick.. not found)

Running: export LD_LIBRARY_PATH=/usr/local/qt5pi/lib/

Fixes this problem but only when logged in as root!

If I export LD_LIBRARY_PATH as user 'pi' I still cannot execute the binary (same error as before).

Stranger still, QtCreator which can deploy and run the binary correctly, is logging in via ssh with user 'pi' !

Any ideas why this is happening?

how long does it took to build on the rpi ? i plan to use nfs to achieve that ... because current snapshots (early august 2012) are before current beta state version ?

--
http://rzr.online.fr//q/armv6

Tomma,

Thanks for the reply. Yes ldd confirms that my executable is an ARM executable :(

Hello there,

Any small hint ?

Please add "[SOLVED]" prefix left to the topic subject. Thanks!

Thanks for your answer. I installed wheezy and it works.

Update your distribution. Glibc is the basis for almost every application in your distribution, so the only reliable way to update it is to update the distribution where everything is then tested with the new glibc.

If you do not want to update your linux: Rebuild Qt Creator, Qt, etc. using your old distribution. That way you get binaries that are compatible with your system.