How to build Qt on system without a GUI?

[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

[Pablo J. Rogina]

@Pavel_47 two things please:

1. Your last screenshot doesn't seem to show exact error, I guess you should scroll up
2. stop posting screenshots, paste text instead (it's easier for others to comment back on any line of output for instance...)

[Pavel_47]

The log is huge.
I scrolled up a few hundred lines - nothing that indicatedŝ errors.
Concerning text instead of screenshots - Ok, I took note.