-qt-xcb failure

[The most recent future]

.configure :

.......
-qt-xcb

---

XLib auto-detection... ()
/usr/local/arm/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-g++ -c -pipe -O2 -Wall -W -fPIE -I../../../mkspecs/linux-arm-gnueabi-g++ -I. -o xlib.o xlib.cpp
xlib.cpp:42:22: fatal error: X11/Xlib.h: No such file or directory
#include <X11/Xlib.h>
^
compilation terminated.
make: *** [xlib.o] Error 1
XLib disabled.
xcb auto-detection... ()
/usr/local/arm/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-g++ -c -pipe -O2 -Wall -W -fPIE -I../../../mkspecs/linux-arm-gnueabi-g++ -I. -o xcb.o xcb.cpp
xcb.cpp:42:21: fatal error: xcb/xcb.h: No such file or directory
#include <xcb/xcb.h>
^
compilation terminated.
make: *** [xcb.o] Error 1
xcb disabled.
The test for linking against libxcb failed!
You might need to install dependency packages for libxcb.
See src/plugins/platforms/xcb/README.

who can help me ?

[jsulm]

@The-most-recent-future You need to install X11 dev packages for your target

[The most recent future]

x11 ? thanks, I try it

[The most recent future]

@jsulm
sudo apt-get install libX11-dev libXext-dev libXtst-dev libXrender-dev libxmu-dev libxmuu-dev

unsolved !, unsolved .
not worked !

[The most recent future]

@jsulm
how install x11 in ubuntu 14 ??

[jsulm]

@The-most-recent-future You need those header files in the sysroot for your target device, not your host PC.

[The most recent future]

@jsulm
thanks , but I do not know those,
could you help find some URL LINK ?
谢谢!

[jsulm]

@The-most-recent-future How do you cross compile? Do you have a sysroot?

[The most recent future]

@jsulm
not sysroot, I do not known what is sysroot, wuwuwuwu.......... crying (),
my cross compile :
/usr/local/arm/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/xxxxxxxx-xx-x-xx

[jsulm]

@The-most-recent-future You need a sysroot if you want to cross compile.
A sysroot is basically the file system of your target device. It is needed to find the header files and libraries for the target.
You should read https://wiki.qt.io/RaspberryPi_Beginners_Guide

[The most recent future]

@jsulm
thanks ， a very nice topic ！
but ,

Look complicated
now,

I just want to install X11, so that the errors of -qt-xcb disappear

[The most recent future]

@jsulm
Requires libxcb >= 1.5.

PACKAGE DEPENDENCIES

Required packages:
libxcb1 libxcb1-dev libx11-xcb1 libx11-xcb-dev libxcb-keysyms1 libxcb-keysyms1-dev libxcb-image0 libxcb-image0-dev libxcb-shm0 libxcb-shm0-dev libxcb-icccm1 libxcb-icccm1-dev libxcb-sync0 libxcb-sync0-dev libxcb-render-util0 libxcb-render-util0-dev libxcb-xfixes0-dev libxrender-dev libxcb-shape0-dev libxcb-randr0-dev libxcb-glx0-dev

On Ubuntu 11.10 icccm1 is replaced by icccm4 and xcb-render-util is not available:
libxcb1 libxcb1-dev libx11-xcb1 libx11-xcb-dev libxcb-keysyms1 libxcb-keysyms1-dev libxcb-image0 libxcb-image0-dev libxcb-shm0 libxcb-shm0-dev libxcb-icccm4 libxcb-icccm4-dev libxcb-sync0 libxcb-sync0-dev libxcb-xfixes0-dev libxrender-dev libxcb-shape0-dev libxcb-randr0-dev libxcb-glx0-dev
The packages for xcb-render-util can be installed manually from http://packages.ubuntu.com/natty/libxcb-render-util0 and http://packages.ubuntu.com/natty/libxcb-render-util0-dev

On Ubuntu 12.04 icccm1 is replaced by icccm4 and xcb-render-util can be installed automatically:
libxcb1 libxcb1-dev libx11-xcb1 libx11-xcb-dev libxcb-keysyms1 libxcb-keysyms1-dev libxcb-image0 libxcb-image0-dev libxcb-shm0 libxcb-shm0-dev libxcb-icccm4 libxcb-icccm4-dev libxcb-sync0 libxcb-sync0-dev libxcb-xfixes0-dev libxrender-dev libxcb-shape0-dev libxcb-randr0-dev libxcb-render-util0 libxcb-render-util0-dev libxcb-glx0-dev

I have all these libraries installed, why also wrong. ???

[jsulm]

@The-most-recent-future AGAIN: you are cross compiling! That means: you need that X11 stuff for your TARGET DEVICE not your development PC! It doesn't matter what you installed on your PC. What you install on your PC cannot be used on your target device (logical isn't it?). That's why I said you should read that link. You need to learn how cross compilation works if you want to cross compile, else you will not succeed.
One of the basic techniques for cross compilation is the sysroot, which contains all needed header files and libraries for the target device.

[jsulm]

@The-most-recent-future What is your target device?

[The most recent future]

@jsulm

, touchscreen . a touchscreen , arm board. samsung soc.

[jsulm]

@The-most-recent-future You need to get a sysroot for it. How, depends on the provider of your device.

[SGaist]

Hi,

As alternative, you can use Qt's bundled xcb. Pass the -qt-xcb parameter to your configure call.

[The most recent future]

@jsulm
thanks ！

QT document is say install xcb， xcb is the same for x 11 ?

[The most recent future]

@SGaist

owowwo ! ~~how to do ? how to do?~~

[The most recent future]

@SGaist
how to do ? please help me , thanks

[SGaist]

Did you pass the option like I suggested ?

[The most recent future]

@SGaist
cryying crying ......
I do not known how to option for you suggested.
please help me .

[SGaist]

path_to_Qt_sources/configure -qt-xcb

[The most recent future]

@SGaist
i do not known ,
path_to_Qt_sources : this is a fnction ? macro ?

[SGaist]

Neither, it's a placeholder that you should replace by the actual path to your Qt sources.

Since you are already building Qt, just do the same as before but replace your -xcb parameter with -qt-xcb.

[The most recent future]

@SGaist
I do not known,
Save me once again ！ 3Q

[SGaist]

Wait wait wait. I think there's been a mis-understanding here (from my side)

You're already configuring Qt with the -qt-xcb option it seems but it seems there something not clean.

Did you do call configure from a clean state ? By clean state I mean either a non configured source tree or from an empty out of source build.

Just in case this page explains what will be provided by the -qt-xcb option.

[The most recent future]

@SGaist
if configuring qt with the -qt-xcb option,
execute ./configure cmd will be failure.
built Qt will be failure,

[SGaist]

Can you show the complete configure line you are using ?

[The most recent future]

@SGaist
./configure -release -opensource -qt-libpng -qt-zlib -qt-libjpeg -qt-xcb -plugin-sql-sqlite -widgets -qt-sql-sqlite -make libs -no-cups -no-nis -no-iconv -no-dbus -no-qml-debug -no-egl -no-opengl -no-icu -no-accessibility -no-javascript-jit -silent -xplatform linux-arm-gnueabi-g++ -arch arm -linuxfb -nomake tools -make examples -nomake tests -qt-freetype -no-glib -strip -plugindir /root/downSource/qt-everywhere-opensource-src-5.2.0/plugins -confirm-license "$@" -verbose

[SGaist]

Ok... What exact backend do you want to use on your target ?

It seems you want to target LinuxFB and X11, is it really the case ? If only LinuxFB then just don't build the xcb backend.

[The most recent future]

@SGaist said in -qt-xcb failure:

If only LinuxFB then just don't build the xcb backend

what ?? why ?
Also please the great gods enlighten me

[The most recent future]

@SGaist
what should I do ？？

[SGaist]

Determine precisely what backend you want to use on your target, as well as what modules you are going to use.

There's absolutely no need to build everything if you are only going to use parts of Qt i.e. if you are only going to use the LinuxFB backend then there's no need to try to build the xcb backend since it's not going to be used. Same goes for QtQuick, QtMultimedia etc. There's no need to waste time and resources to build something you're not going to use.

Also, I currently don't see any reason for you to set the -plugindir option. Just drop it, the default should be enough.

[The most recent future]

@SGaist
Hi SGaist ！

libQt5DBus.so.5 not find ，
Where the path is libQt5DBus.so.5 ?
I will put hte so to the /usr/lib

[The most recent future]

@SGaist
Hi SGaist ！

libQt5DBus.so.5 not find ，
Where the path is libQt5DBus.so.5 ?
I will put hte so to the /usr/lib

[SGaist]

There's no use at posting twice the same answer in a two hour interval, that won't make things go faster.

You passed the -no-dbus flag as configure option.

Like I already wrote before: take a step back, write down what you really need from Qt and then we can get a constructive conversation.