It appears that qdoc links against libclang dynamically. As a consequence the binary we ship in our packages do not run out of the box. How to reproduce:
1. Install the 5.11 alpha binaries via the Qt online installer.
2. Try to run the qdoc binary:
We need to either link statically against libclang or ship the binaries and link with rpath.
The same problem exists on Windows, where any attempt of trying to run qdoc.exe results in a message box with the test "The code execution cannot proceed because libclang.dll was not found. Reinstalling the program may fix this problem.".
The binaries we shipped in 5.10 used to work, so this is a regression.
We cannot provide binaries of qdoc if the host compiler is MinGW 5.3.0 and we use static linkage. That means our official x86-64 MinGW packages, our Qt/Android Windows packages and our Qt/QNX Windows will not contain qdoc and users of those packages will not be able to build document of their own application/library (or of Qt itself).
The reason as to why we can't simply perform this build is because libclang is built with MinGW 7.1 (despite the Jenkins stages claiming that it's 5.3) and thus uses symbols from libstdc++ that are new in that version and not present in libstdc++ in 5.3.0 (as undefined symbol references to std::thread::_State::~_State indicate). Unfortunately we cannot build libclang with MinGW 5.3.0 as the compiler crashes during the build.
So the only path to restore qdoc binaries with the chosen approach is to upgrade the MinGW build of Qt to use MinGW 7.1 or newer. Whether that is an acceptable option for the 5.11.0 release is something that needs to be discussed now. If the decision is to ship 5.11.0 without qdoc for the affected builds, then the next question would be: Is an upgrade of MinGW to 7.1 an acceptable option for a patch release of Qt (5.11.x) ?
Conclusion: MinGW and Qt/Android|QNX packages on Windows will ship without qdoc in 5.11.0. MinGW 7.3 builds will be added in parallel to 5.3.0 to Qt for 5.11.1 and then qdoc will be re-enabled for those configurations. Follow-up bugs created and linked from here.