[Unresolved] Correct way to compile Qt for Raspberry Pi



  • I have built Qt 5.5 from source using this configuration line:
    ./configure -opensource -nomake examples -nomake tests -release** -opengl es2**
    I have obtained this

    OpenGL / OpenVG:
    EGL .................. yes
    OpenGL ............... yes (OpenGL ES 2.0+)
    OpenVG ............... no
    PCRE ................... yes (bundled copy)
    pkg-config ............. yes
    PulseAudio ............. yes
    QPA backends:
    DirectFB ............. no
    EGLFS ................ yes
    EGLFS i.MX6....... . no
    EGLFS KMS .......... no
    EGLFS Mali ......... no
    EGLFS Raspberry Pi . no
    EGLFS X11 .......... yes
    LinuxFB .............. yes
    XCB .................. yes (system library)
    EGL on X ........... yes
    GLX ................ yes
    MIT-SHM ............ yes
    Xcb-Xlib ........... yes
    Xcursor ............ yes (loaded at runtime)
    Xfixes ............. yes (loaded at runtime)
    Xi ................. no
    Xi2 ................ yes
    Xinerama ........... yes (loaded at runtime)
    Xrandr ............. yes (loaded at runtime)
    Xrender ............ yes
    XKB ................ no
    XShape ............. yes
    XSync .............. yes
    XVideo ............. yes

    but still, after recompilation, my qml app eats one core to show a timer.
    %CPU %MEM TIME+ COMMAND
    90,4 5,2 7:02.34 LocalClock
    **8,6 ** 1,4 0:37.63 Xorg
    Have I made a mistake? Do I need anything else to speedup my app?



  • I see a lot of videos in youtube using X11, OpenGL ES and Quick 2 but I haven't got any idea on how it can be possible.
    I'm considering to come back to qtwidgets.



  • Up to now seems to be impossible.
    The only way is to use Wayland 1.4, to have opengl es for Quick 2. But in the official Raspberry Pi debian image there is Wayland 1.0.
    Without Wayland 1.4 only Quick 1 is available.



  • After 2 week to hard working..

    Upgrading my Raspberry Pi from Debian 7 (wheezy) to debian 8 (Jessie) I can compile Qt 5.5.0 with wayland support.
    Now, starting my application on a weston console I obtain the errors:

    libEgl warning: failed to create shm screen
    failed to initialize EGL display...
    Any idea?



  • @mrdebug

    Using this post I managed to compile on the raspberry pi it took me 5 days as it was taking so long to compile even with over clocking. But then I wasn't using a b+ so have no idea how long it would take with that. But I was able to compile and run the opengl example programs. It was a little slow but it worked. Once the app was running it was fine.

    https://forum.qt.io/topic/29765/qt5-1-on-rasberry-pi-full-install-not-cross-compile/6



  • Thank you for the reply but my problem is not build Qt but having Quick 2 working in Raspberry Pi.



  • @wozza

    never compile something on Raspberry is just a waste of time, compile your application on your PC and then send the executable with the needed libraries to Raspberry. Yes, I know that the architectures of processor is not the same, the solution is to use either crosscompiler, or Docker.

    I have made a docker image for raspberry, which will enable you to compile your Qt application as if you are doing it in a raspberry and then copy the executable and send it to your raspberry, here is the link

    https://hub.docker.com/r/theshadowx/rpiqt/



  • My problem is different.
    I haven't got any problem to compile something for Raspberry Pi, using a real Raspberry Pi or something else.
    The problem is to run a Qt Quick 2 application in a Raspberry Pi.
    Qt Quick 2 wants OpenGL ES but up to now OpenGL ES is not available in Raspberry Pi.
    You can try Debian 8 Jessie with weston but the application crashes at startup.
    Up to now (imho) is possible to use only QtWidgets or console programs.
    I have tried for many weeks with Debian 8 Jessie and Qt 5.5.0 without find a solution.



  • @mrdebug which raspberry Pi are you using ?



  • Raspberry Pi Model B+
    Raspberry Pi 2 Modello B Quad Core


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.