-qt-xcb failure
-
Hi,
As alternative, you can use Qt's bundled xcb. Pass the
-qt-xcbparameter to your configure call.@SGaist
how to do ? please help me , thanks -
Did you pass the option like I suggested ?
-
@SGaist
cryying crying ......
I do not known how to option for you suggested.
please help me . -
path_to_Qt_sources/configure -qt-xcb -
@SGaist
i do not known ,
path_to_Qt_sources : this is a fnction ? macro ? -
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
-xcbparameter with-qt-xcb. -
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
-xcbparameter with-qt-xcb.@SGaist
I do not known,
Save me once again ！ 3Q -
Wait wait wait. I think there's been a mis-understanding here (from my side)
You're already configuring Qt with the
-qt-xcboption 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-xcboption. -
Wait wait wait. I think there's been a mis-understanding here (from my side)
You're already configuring Qt with the
-qt-xcboption 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-xcboption.@SGaist
if configuring qt with the -qt-xcb option,
execute ./configure cmd will be failure.
built Qt will be failure, -
Can you show the complete configure line you are using ?
-
@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 -
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.
-
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.
@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 -
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.
@SGaist
what should I do ？？ -
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
-plugindiroption. Just drop it, the default should be enough. -
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
-plugindiroption. Just drop it, the default should be enough.@SGaist
Hi SGaist ！libQt5DBus.so.5 not find ，
Where the path is libQt5DBus.so.5 ?
I will put hte so to the /usr/lib -
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
-plugindiroption. Just drop it, the default should be enough.@SGaist
Hi SGaist ！libQt5DBus.so.5 not find ，
Where the path is libQt5DBus.so.5 ?
I will put hte so to the /usr/lib -
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-dbusflag 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.
