How to build Qt on system without a GUI?

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

[SGaist]

Run the build with only one process you'll have the error closer.

[Pavel_47]

Yes, with one core the the log is more verbose.
Here is what I got at the end:

rm -f libcomposeplatforminputcontextplugin.so
/home/pavel/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf-g++ -mfloat-abi=hard --sysroot=/home/pavel/raspi/sysroot -Wl,--no-undefined -Wl,-O1 -Wl,--enable-new-dtags -Wl,-z,origin -Wl,-rpath,\$ORIGIN/../../lib -Wl,-rpath-link,/home/pavel/raspi/sysroot/opt/vc/lib -Wl,-rpath-link,/home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf -Wl,-rpath-link,/home/pavel/raspi/sysroot/lib/arm-linux-gnueabihf -shared -o libcomposeplatforminputcontextplugin.so .obj/qcomposeplatforminputcontextmain.o .obj/qcomposeplatforminputcontext.o .obj/moc_qcomposeplatforminputcontext.o  -L=/opt/vc/lib /home/pavel/raspi/qtbase/lib/libQt5Gui.so /home/pavel/raspi/qtbase/lib/libQt5Core.so /home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libGLESv2.so -lpthread /home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libxkbcommon.so   
.obj/qcomposeplatforminputcontext.o: In function `QComposeInputContext::~QComposeInputContext()':
qcomposeplatforminputcontext.cpp:(.text+0x34): undefined reference to `xkb_compose_state_unref'
qcomposeplatforminputcontext.cpp:(.text+0x3c): undefined reference to `xkb_compose_table_unref'
.obj/qcomposeplatforminputcontext.o: In function `QComposeInputContext::reset()':
qcomposeplatforminputcontext.cpp:(.text+0x80): undefined reference to `xkb_compose_state_reset'
.obj/qcomposeplatforminputcontext.o: In function `QComposeInputContext::ensureInitialized()':
qcomposeplatforminputcontext.cpp:(.text+0x3bc): undefined reference to `xkb_compose_table_new_from_locale'
qcomposeplatforminputcontext.cpp:(.text+0x3d0): undefined reference to `xkb_compose_state_new'
.obj/qcomposeplatforminputcontext.o: In function `QComposeInputContext::filterEvent(QEvent const*)':
qcomposeplatforminputcontext.cpp:(.text+0x6ac): undefined reference to `xkb_compose_state_feed'
qcomposeplatforminputcontext.cpp:(.text+0x6b4): undefined reference to `xkb_compose_state_get_status'
qcomposeplatforminputcontext.cpp:(.text+0x6f8): undefined reference to `xkb_compose_state_get_utf8'
qcomposeplatforminputcontext.cpp:(.text+0x72c): undefined reference to `xkb_compose_state_get_utf8'
collect2: error: ld returned 1 exit status
Makefile:247: recipe for target '../../../../plugins/platforminputcontexts/libcomposeplatforminputcontextplugin.so' failed
make[4]: *** [../../../../plugins/platforminputcontexts/libcomposeplatforminputcontextplugin.so] Error 1
make[4]: Leaving directory '/home/pavel/raspi/qtbase/src/plugins/platforminputcontexts/compose'
Makefile:47: recipe for target 'sub-compose-make_first' failed
make[3]: *** [sub-compose-make_first] Error 2
make[3]: Leaving directory '/home/pavel/raspi/qtbase/src/plugins/platforminputcontexts'
Makefile:129: recipe for target 'sub-platforminputcontexts-make_first' failed
make[2]: *** [sub-platforminputcontexts-make_first] Error 2
make[2]: Leaving directory '/home/pavel/raspi/qtbase/src/plugins'
Makefile:778: recipe for target 'sub-plugins-make_first' failed
make[1]: *** [sub-plugins-make_first] Error 2
make[1]: Leaving directory '/home/pavel/raspi/qtbase/src'
Makefile:50: recipe for target 'sub-src-make_first' failed
make: *** [sub-src-make_first] Error 2

Seem that problem is still related to xkb staff ...

[jsulm]

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

undefined reference to `xkb_compose_state_get_utf8'

You're not linking against xkb lib

[Pavel_47]

So, problems in Makefile ?

[jsulm]

@Pavel_47 Try

file /home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libxkbcommon.so

and post the output here.

[Pavel_47]

here it is:

pavel@ALABAMA:~/raspi/qtbase$ file ~/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libxkbcommon.so
/home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libxkbcommon.so: symbolic link to libxkbcommon.so.0.0.0

[jsulm]

@Pavel_47 Then please do

file /home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libxkbcommon.so.0.0.0

[Pavel_47]

pavel@ALABAMA:~/raspi/qtbase$ file ~/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libxkbcommon.so.0.0.0
/home/pavel/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libxkbcommon.so.0.0.0: cannot open `/home/pavel/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libxkbcommon.so.0.0.0' (No such file or directory)

[Pablo J. Rogina]

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

I've just checked libxkbcommon-dev and libxkbcommon-x11-dev on RPi.

So sync them to your sysroot in the host PC!

As on Ubuntu they are installed and are newest versions.

Forget about that, it doesn't matter.

For cross-compilation you need your libraries + headers installed properly in target device (RPi), then copy (synchronize) some folders from your target device into the sysroot folder in your host PC (with Ubuntu) and only then attempt to build (Qt framework, modules, your application).

Please take a look at this guide for cross-compiling Qt for RPi

[Pavel_47]

@Pablo-J-Rogina said in How to build Qt on system without a GUI?:

Please take a look at this guide for cross-compiling Qt for RPi

I proceeded exactly as described on the page you mentioned.
Sure I performed the resync with RPi

[Pablo J. Rogina]

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

Sure I performed the resync with RPi

I'm not going to argue in contrary, so your next task is to figure out why even having rsync'd the file is missing from your sysroot folder...

/home/pavel/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libxkbcommon.so.0.0.0: cannot open

[Pavel_47]

The file isn't missing. It's there: