How to build Qt on system without a GUI?

[BrMisha]

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

[closx]

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

fatal error: xkbcommon/xkbcommon-compose.h: No such file or directory

Like @SGaist said, you need the libraries anyway. Check Qt5 Dependencies page.
Try this maybe?

sudo apt-get install libx11-xcb-dev libglu1-mesa-dev build-dependencies

If not solves, try this,

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

[SGaist]

@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]

@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]

@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]

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]

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]

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

I installed this libs

dev package also (which contains header files)?

[BrMisha]

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

[SGaist]

Did you re-run configure from a clean state ?

[BrMisha]

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

[SGaist]

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

[BrMisha]

Log i will saw after do configure?

[SGaist]

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

[Pavel_47]

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]

Hi,

What version of xkbcommon do you have installed ?

[Pavel_47]

@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]

@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]

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]

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]

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]

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.

[Pavel_47]

I've just checked libxkbcommon-dev and libxkbcommon-x11-dev on RPi. As on Ubuntu they are installed and are newest versions.

[SGaist]

Did you sync your RPi filesystem back to your host before trying to build Qt ?

[Pavel_47]

Yes, at very first time I executed these commands (as it's suggested here https://wiki.qt.io/RaspberryPi2EGLFS):
rsync -avz pi@raspberrypi.local:/lib sysroot
rsync -avz pi@raspberrypi.local:/usr/include sysroot/usr
rsync -avz pi@raspberrypi.local:/usr/lib sysroot/usr
rsync -avz pi@raspberrypi.local:/opt/vc sysroot/opt

Then I did 3 or 4 other attempts to build, but at each of these attempts I didn't proceed with resync with RPi.
Anyway one thing escapes me .... should I keep connection with RPi while running toolchain build on host ?

[jsulm]

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

should I keep connection with RPi while running toolchain build on host ?

No, you just need to sync your sysroot.

[Pavel_47]

I've checked the location of xkbcommon-compose.h. It's Ok:

Then I've tried to compile this:

#include <xkbcommon/xkbcommon-compose.h>
int main() {}

It was also Ok

[jsulm]

@Pavel_47 Is it in your host system or sysroot?

[Pavel_47]

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

@Pavel_47 Is it in your host system or sysroot?

Sorry, I didn't understand what you mean ...
The location of the screenshot: /usr/include/xkbcommon on my host
The location of .c snippet (where I compiled it): ~/raspi/ on my host

[jsulm]

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

/usr/include/xkbcommon on my host

That's the point: you need these headers in your sysroot!

[Pavel_47]

Indeed !
In ~/raspi/sysroot/usr/include/xkbcommon there is one less file comparing to /usr/include/xkbcommon ... and this missed file is precisely xkbcommon-compose.h.

So, I copy xkbcommon-compose.h from /usr/include/xkbcommon to ~/raspi/sysroot/usr/include/xkbcommon and then build Qt toolchain once more ?

[Pavel_47]

I copied xkbcommon-compose.h from /usr/include/xkbcommon to ~/raspi/sysroot/usr/include/xkbcommon and then run make once more.
And it failed one more time.
Here is how it finished:

Any other suggestions ?

Thanks.

[SGaist]

As we already wrote: you need the library too. And built for your target.

[Pavel_47]

You mean that the errors announce in the screenshot from previous message are still related to the xkbcommon issue ?
So I should ask xkbcommon developpers for makefile dedicated for RPi3. Correct ?
Let's say I got it, what next ? Where should I put xkbcommon built directory ... i.e. which location in ~/raspi/sysroot.
After all ... I wonder if someone already faced this issue ? Or this probles rose for the 1st time ? What about previous Qt releases ? There were no similar issues ?

[SGaist]

It's a library that is now provided on all Linux flavours supported by the Qt project. Prior to that, it was bundled with Qt.

So what distribution are you running on your Pi ?

[Pavel_47]

Linux raspberrypi 4.9.77-v7+

[SGaist]

That's the kernel running on your target.

Are you using Raspbian ? Another distribution ?

[Pavel_47]

Yes, I use raspbian "Jessie"

[SGaist]

Then, AFAIR, you should have the library. So if it can't be found either:

• it wasn't synchronized properly back to your host machine
• the configure call has not been done from a clean state
• it's not the correct library that was found

For the first point you have to sync the library as well as the symbolic links pointing to it or re-create them in your host copy of the sysroot.

[Pavel_47]

I did as you suggested:
(1) resync host wit RPi:
rsync -avz pi@raspberrypi.local:/lib sysroot
rsync -avz pi@raspberrypi.local:/usr/include sysroot/usr
rsync -avz pi@raspberrypi.local:/usr/lib sysroot/usr
rsync -avz pi@raspberrypi.local:/opt/vc sysroot/opt
(2) update symbolic names:
./sysroot-relativelinks.py sysroot
Then rebuild Qt (rather tried to rebuild).
Here is what I got:

This time it's different ... but still fails