-qt-xcb failure

[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.