[Interest] Bootstrapped qdbuscpp2xml (unregistered input type QDBusMessage)

[Jörn M]

I found following closed bugreport. It seems to be known that bootstrapped
version of qdbuscpp2xml does not support all types (first comment)

https://bugreports.qt.io/browse/QTBUG-5744

In this case bootstrapped qdbuscpp2xml is only usable for building qt
itself.

Is this correct?

Yocto layer meta-qt5 for example builds qtbase-native tools bootstrapped
and further packages use the provided tools.

Is it wrong to use the bootstrapped tools in this case?

Jörn M <joern477 at gmail.com> schrieb am Di., 27. März 2018, 20:58:

> Hello together,
>
> when creating a native qtbase toolchain you get a bootstrapped version
> of the tools (qdbuscpp2xml) after compiling with following configure cmd:
>
> https://paste.kde.org/p5r8axfuy
>
> ldd ./qdbuscpp2xml
> linux-vdso.so.1 =>  (0x00007ffd1b34e000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x00007f264bac0000)
> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x00007f264b73e000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f264b435000)
> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f264b21f000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f264ae55000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f264bcdd000)
>
> and a non bootstrapped version with:
>
> https://paste.kde.org/prxxl8sef
>
> ldd ./qdbuscpp2xml
> linux-vdso.so.1 =>  (0x00007ffc32d77000)
> libQt5DBus.so.5 => /home/joern/yocto/qtbaseMaster/lib/libQt5DBus.so.5
> (0x00007fa64feb0000)
> libQt5Core.so.5 => /home/joern/yocto/qtbaseMaster/lib/libQt5Core.so.5
> (0x00007fa64f735000)
> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x00007fa64f3b3000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa64efe9000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x00007fa64edcc000)
> libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3
> (0x00007fa64eb80000)
> libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fa64e966000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa64e762000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa64e459000)
> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa64e243000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fa64fd1c000)
> libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0
> (0x00007fa64fdf4000)
> libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1
> (0x00007fa64e021000)
> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fa64de19000)
> liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fa64dbf7000)
> libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20
> (0x00007fa64d916000)
> libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fa64d6a6000)
> libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
> (0x00007fa64d492000)
>
>
> The non bootstrapped version of qdbuscpp2xml works fine and generates
> correct xml for:
>
> https://cgit.kde.org/baloo.git/tree/src/file/filecontentindexer.h
>
> ./qdbuscpp2xml -a filecontentindexer.h -o test.xml
>
> The bootstrapped version instead outputs the following:
>
> ./qdbuscpp2xml -a filecontentindexer.h -o test.xml
> Unregistered input type in parameter list: QDBusMessage
> Unregistered input type in parameter list: QDBusMessage
>
> The generated xml misses the interfaces for:
>
>     Q_SCRIPTABLE void registerMonitor(const QDBusMessage& message);
>     Q_SCRIPTABLE void unregisterMonitor(const QDBusMessage& message);
>
> Is this an already known issue? (I've tested this with 5.9.4, 5.10.1 and latest 5.11, all with the same result.)
>
> Best Regards,
> Jörn
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20180328/3a586338/attachment.html>