[Development] Lots of qdoc-related warning messages when building 'docs' target in Qt-6.6.0?

[Kai Köhne]

Hi,

QDoc needs to parse C++ sources to actually generate the API documentation. This requires a build where
the modules are actually configured. This explains some of the warnings you see - Qt WebEngine, Qt PDF cannot be built on MinGW, and likewise Qt Wayland (Compositor).

Anyway, like Paul said, there are also some warnings even in the official builds ...

Kai

________________________________________
From: Development <development-bounces at qt-project.org> on behalf of Haowei Hsu <hwhsu1231 at gmail.com>
Sent: Sunday, October 22, 2023 5:21
To: Paul Wicking
Cc: development at qt-project.org
Subject: Re: [Development] Lots of qdoc-related warning messages when building 'docs' target in Qt-6.6.0?

Hello, Paul.

I've read https://doc.qt.io/qt-6/qdoc-warnings.html, but still don't figure it out.
BTW, I also tried to build docs of Qt-6.5.3, and still encountered the same problem. For example:

C:/Test/qt-everywhere-src-6.5.3/qtbase/src/gui/image/qicon.cpp:1152: (qdoc) warning: Can't link to 'fallbackIconTheme()'
C:/Test/qt-everywhere-src-6.5.3/qtbase/src/gui/image/qicon.cpp:1171: (qdoc) warning: Can't link to 'fallbackIconTheme()'
C:/Test/qt-everywhere-src-6.5.3/qtbase/src/gui/kernel/qaction.cpp:139: (qdoc) warning: Can't link to 'Qt Widgets - Application Example'

and

C:/Test/qt-everywhere-src-6.5.3/qtdoc/doc/src/qtmodules.qdoc:4: (qdoc) warning: Can't link to 'Qt PDF'
C:/Test/qt-everywhere-src-6.5.3/qtdoc/doc/src/qtmodules.qdoc:4: (qdoc) warning: Can't link to 'Qt WebEngine'
C:/Test/qt-everywhere-src-6.5.3/qtdoc/doc/src/qtmodules.qdoc:4: (qdoc) warning: Can't link to 'Qt Wayland Compositor'
C:/Test/qt-everywhere-src-6.5.3/qtdoc/doc/src/wayland-and-qt.qdoc:4: (qdoc) warning: Can't link to 'Qt Wayland Compositor'

You can see the full logs in attachment: LOG-still-has-the-qdoc-warning-in-qt-6.5.3.txt
Therefore, I think this problem might not be a bug.
Instead, I think it's probably because I missed something, but I don't know which part is missing.
Could it be that I forgot to add some paths to a specific environment variable?

---
Haowei Hsu