How to build Qt on system without a GUI?

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