How to build Qt on system without a GUI?

SGaist · wrote on 3 Jul 2019, 06:42

@BrMisha said in How to build Qt on system without a GUI?:

https://forum.qt.io/topic/45821/building-minimal-qt5-no-gui-just-qtcore-qtnetwork-oh-and-qtscript-solved/2
This man had like problem. He wrote that built qtbase, bu HOW??? I can't find info about it on network

Run the configure script that is located in qtbase.

As for xkbcommon, you can also disable that feature.

BrMisha · 3 Jul 2019, 11:42

@closx said in How to build Qt on system without a GUI?:

libraries
I installed this libs and started make. Now waiting a few hours ))) (it's quit slow)

BrMisha · 7 Mar 2019, 09:34

@SGaist so, i have done it but got this output:

rm -f libqvnc.so
g++ -Wl,--no-undefined -Wl,-O1 -Wl,--enable-new-dtags -Wl,-z,origin -Wl,-rpath,\$ORIGIN/../../lib -shared -o libqvnc.so .obj/main.o .obj/qvncintegration.o .obj/qvncscreen.o .obj/qvnc.o .obj/qvncclient.o .obj/moc_qvncscreen.o .obj/moc_qvnc_p.o .obj/moc_qvncclient.o  /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5ServiceSupport.a /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5ThemeSupport.a /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5FbSupport.a /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5EventDispatcherSupport.a /usr/lib/arm-linux-gnueabihf/libgthread-2.0.so /usr/lib/arm-linux-gnueabihf/libglib-2.0.so /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5FontDatabaseSupport.a /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libqtfreetype.a /usr/lib/arm-linux-gnueabihf/libpng12.so /usr/lib/arm-linux-gnueabihf/libz.so /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5InputSupport.a /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5Gui.so /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5DeviceDiscoverySupport.a /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5Network.so /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5DBus.so /home/analog/qt-everywhere-src-5.13.0/qtbase/lib/libQt5Core.so /usr/lib/arm-linux-gnueabihf/libGL.so -lpthread
mv -f libqvnc.so ../../../../plugins/platforms/libqvnc.so
make[5]: Leaving directory `/home/analog/qt-everywhere-src-5.13.0/qtbase/src/plugins/platforms/vnc'
make[4]: Leaving directory `/home/analog/qt-everywhere-src-5.13.0/qtbase/src/plugins/platforms'
make[3]: Leaving directory `/home/analog/qt-everywhere-src-5.13.0/qtbase/src/plugins'
make[2]: *** [sub-plugins-make_first] Error 2
make[2]: Leaving directory `/home/analog/qt-everywhere-src-5.13.0/qtbase/src'
make[1]: *** [sub-src-make_first] Error 2
make[1]: Leaving directory `/home/analog/qt-everywhere-src-5.13.0/qtbase'
make: *** [module-qtbase-make_first] Error 2

SGaist · wrote on 3 Jul 2019, 09:58

This doesn't show where the build failed.

Re-run the build without the -j parameter so you'll see exactly were the error is.

BrMisha · wrote on 3 Jul 2019, 10:39

In file included from qcomposeplatforminputcontextmain.cpp:44:0:
qcomposeplatforminputcontext.h:46:41: fatal error: xkbcommon/xkbcommon-compose.h: No such file or directory
 #include <xkbcommon/xkbcommon-compose.h>

jsulm · 3 Jul 2019, 17:01

@BrMisha said in How to build Qt on system without a GUI?:

I installed this libs

dev package also (which contains header files)?

BrMisha · J jsulm 3 Jul 2019, 11:42

@jsulm yes, libxkbcommon0 libxkbcommon-x11-dev libxkbcommon-dev are installed

SGaist · 4 Jul 2019, 03:29

Did you re-run configure from a clean state ?

BrMisha · S SGaist 3 Jul 2019, 21:43

@SGaist I did re-unzip sources, then did configure))

SGaist · wrote on 4 Jul 2019, 20:07

Can you check the configure log to see if there's anything related to that ?

BrMisha · wrote on 5 Jul 2019, 05:22

Log i will saw after do configure?

SGaist · wrote on 5 Jul 2019, 21:53

They are generated when configure is run. Look into your build folder.

Pavel_47 · wrote on 23 Oct 2019, 14:19

Hello,
I've tried all suggestions found on this topic, but build process still fails: cannot find xkbccommon-compose.h file. Just one remark: trying to install additional packages with the command:
sudo apt-get install libxcb1 libxcb-util0 libpam-dev ...
I should remove just libxbc-util0 (all others were kept) because this package wasn't found.
Any ideas ?
Thanks.

SGaist · wrote on 23 Oct 2019, 18:07

Hi,

What version of xkbcommon do you have installed ?

Pavel_47 · 24 Oct 2019, 09:01

@closx said in How to build Qt on system without a GUI?:
I'm not aware what is actually installed ... I've just executed the following instruction, as was suggested previously in this topic (except libxcb-util0 which wasn't found)

sudo apt-get install libxcb1 libxcb-util0 libpam-dev libcairo-dev libxcb-xinerama0 libev-dev libx11-dev libx11-xcb-dev libxkbcommon0 libxkbcommon-x11-dev libxkbcommon-dev libxcb-dpms0-dev libxcb-xinerama0-dev libxkbfile-dev libxcb-util0-dev libxcb-image0-dev

jsulm · wrote on 24 Oct 2019, 09:01

@Pavel_47 Did you install these packages on your target device? Since you're crosscompiling you need them in your sysroot, not on your host machine.

Pavel_47 · wrote on 24 Oct 2019, 09:15

I've contacted libxkbcommon developers. They suggested me using this command:
sudo apt-get install libxkbcommon-dev libxkbcommon-x11-dev
That is what i did, but system informed me that libxkbcommon-dev and libxkbcommon-x11-dev are already the newest versions (i.e. 0.8.2-1~ubuntu 18.04.1).

Well, I'm trying to rebiuild Qt toolchain once more . Now it's running ...

Pavel_47 · wrote on 24 Oct 2019, 09:26

Sorry, I've missed your last suggestion - install libxkbcommon on target (i.e RPi3 in my case). But anyway, how build process on the host can be influenced by what is installed (or not) on that target device ?

Pavel_47 · wrote on 24 Oct 2019, 09:42

The new attempt of Qt building is also failed.
I wonder if anyone has managed to bulid Qt on Ubuntu ?
What should I check ... or install to resolve the problem ?

SGaist · wrote on 24 Oct 2019, 10:51

Since you are cross-compiling, you need all dependencies for your target. This is usually done installing the libraries on said target and then sync the content of the file system of the target back to the host so the cross-compiler can use them to do its work.