Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#61475 - [qt5-doc] Missing documentation
Attached to Project:
Arch Linux
Opened by Martin Sandsmark (sandsmark) - Sunday, 20 January 2019, 10:01 GMT
Last edited by Antonio Rojas (arojas) - Friday, 14 June 2019, 14:08 GMT
Opened by Martin Sandsmark (sandsmark) - Sunday, 20 January 2019, 10:01 GMT
Last edited by Antonio Rojas (arojas) - Friday, 14 June 2019, 14:08 GMT
|
DetailsLatest version (5.12.0) of qt5-doc is missing documentation for functions in some classes. Seems to be mostly "simple" classes, e. g. QRect/QRectF, QReadLocker, QQueue, QStack.
There's also some missing links, e. g. to «Threading Classes» in the Qt Core module overview. I noticed it in Qt Assistant, but I checked and it seems to be missing from the generated HTML as well, so it's not just something incompatible with the renderer in Assistant. One possible reason could be if clang fails to parse the source when building the documentation, but because this only leads to warnings and not build failure, AFAIK, it's easy to miss. Especially since there are a lot of "expected" warnings as well. |
This task depends upon
Closed by Antonio Rojas (arojas)
Friday, 14 June 2019, 14:08 GMT
Reason for closing: Fixed
Additional comments about closing: Qt 5.12.4
Friday, 14 June 2019, 14:08 GMT
Reason for closing: Fixed
Additional comments about closing: Qt 5.12.4
And clang has been upgraded to 7.0.1 since the current qt5-doc package was built, so I assume this new clang version broke the qt5-doc building.
https://bugreports.qt.io/browse/QTBUG-72517
The error messages matches this, but the cause of it could be something completely different.
I really hope this is not another case of Qt relying of specific features of their own clang fork
> pacman -Ql qt5-doc
...
/usr/share/doc/qt/qtcore/qrect.html
/usr/share/doc/qt/qtcore/qrectf.html
...
/usr/share/doc/qt/qtcore/qreadlocker.html
...
/usr/share/doc/qt/qtcore/qqueue.html
...
/usr/share/doc/qt/qtcore/qstack.html
...
Are you sure you weren't using a self-built package?
Since I kind of ruled out packaging issues, I filed an upstream bug report here: https://bugreports.qt.io/browse/QTBUG-73150