Important: Please read the Qt Code of Conduct -

[Solved] How to configure QT5 so that Linucfb does not contain x11 and xcb?

  • The plugin Linuxfb includes x11 and xcb (detected by command ldd). is there any solution to exclude x11 and xcb? if yes, how to configure QT5?

    My configure: (I don't know whether these parameters are correct)
    -opensource -confirm-license -c++11 -shared -largefile -qml-debug -mtdev -optimized-qmake -gui -widgets
    -no-icu -no-glib -no-cups -no-gtkstyle -no-journald
    -qt-pcre -qt-libpng -qt-libjpeg -qt-freetype -qt-harfbuzz
    -opengl -xcb -directfb -linuxfb
    -nomake tests -nomake examples

    root@linuxdevelopos:/platforms# **ldd ./ ** => (0xb770f000) => /usr/lib/i386-linux-gnu/ (0xb7673000) => /usr/lib/i386-linux-gnu/ (0xb75d3000) => /lib/i386-linux-gnu/ (0xb74c6000) => /lib/i386-linux-gnu/ (0xb74b3000) => /usr/lib/i386-linux-gnu/ (0xb705b000) => /usr/lib/i386-linux-gnu/ (0xb6bc5000) => /lib/i386-linux-gnu/ (0xb6ba9000) => /usr/lib/i386-linux-gnu/ (0xb6ac0000) => /lib/i386-linux-gnu/ (0xb6912000) => /lib/i386-linux-gnu/ (0xb68e9000) => /lib/i386-linux-gnu/ (0xb68cf000) => /lib/i386-linux-gnu/ (0xb68a7000) => /lib/i386-linux-gnu/ (0xb6868000) => /lib/i386-linux-gnu/ (0xb684a000) => /lib/i386-linux-gnu/ (0xb6831000) => /lib/i386-linux-gnu/ (0xb6827000) => /lib/i386-linux-gnu/ (0xb67dc000) => /lib/i386-linux-gnu/ (0xb67d2000)
    /lib/ (0xb7710000) => /usr/lib/i386-linux-gnu/ (0xb677c000) => /usr/lib/i386-linux-gnu/mesa/ (0xb671c000) => /lib/i386-linux-gnu/ (0xb66d6000) => /lib/i386-linux-gnu/ (0xb66b9000) => /usr/lib/i386-linux-gnu/ (0xb64ab000) => /usr/lib/i386-linux-gnu/ (0xb6339000) => /lib/i386-linux-gnu/ (0xb6334000) => /usr/lib/i386-linux-gnu/ (0xb6318000) => /usr/lib/i386-linux-gnu/ (0xb62ff000) => /usr/lib/i386-linux-gnu/ (0xb62ec000) => /usr/lib/i386-linux-gnu/ (0xb62e8000) => /usr/lib/i386-linux-gnu/ (0xb62e2000) => /usr/lib/i386-linux-gnu/ (0xb62df000) => /usr/lib/i386-linux-gnu/ (0xb61ab000) => /usr/lib/i386-linux-gnu/ (0xb6192000) => /usr/lib/i386-linux-gnu/ (0xb618c000) => /usr/lib/i386-linux-gnu/ (0xb6188000) => /usr/lib/i386-linux-gnu/ (0xb6184000) => /usr/lib/i386-linux-gnu/ (0xb617d000) => /usr/lib/i386-linux-gnu/ (0xb615a000) => /usr/lib/i386-linux-gnu/ (0xb6157000) => /usr/lib/i386-linux-gnu/ (0xb6151000) => /usr/lib/i386-linux-gnu/ (0xb6143000) => /usr/lib/i386-linux-gnu/ (0xb4ad6000) => /usr/lib/i386-linux-gnu/ (0xb4ad1000) => /usr/lib/i386-linux-gnu/ (0xb4aca000)

  • Lifetime Qt Champion


    Replace -xcb with -no-xcb

  • @SGaist Thanks for reply. I've replaced -xcb with -no-xcb, but it still contains xcb and x11 after configure.

  • Lifetime Qt Champion

    Did you do it from a clean tree ? e.g. after make confclean ?

  • @SGaist Yes, everytime I try these operations based on a clean start. I delete all old directories and uncompress the clean codes

  • The plugin is not supposed to contain cxb and x11, as it is based on framebuffer. I’ve compiled many times but ldd still detects that includes xcb and x11. The weird thing is that I also tired –no-xcb while executing configure, but that seems doesn’t work.
    I’m using x86 embedded platform.

  • Lifetime Qt Champion

    I'm just realizing, ldd is finding your system Qt before the one you built, so the xcb related decencies come from your system QtGui library not from the one you built. Add LD_LIBRARY_PATH=/path/to/your/selfbuiltqt/lib before calling ldd

  • @SGaist Thant does not work. Is it a QT bug?

  • Lifetime Qt Champion

    How did you apply my suggestion ?

  • @SGaist everything is OK now after executing make install. I didn't execute it before, thus I think that's the reason.
    Thank you very much!

  • Lifetime Qt Champion

    Then indeed, you were testing the libraries from your old build ;)

    Happy coding !

Log in to reply