Details
-
Bug
-
Resolution: Duplicate
-
P2: Important
-
None
-
5.11.0, 5.11.1
-
None
-
- Original discovery configuration:
- OS X 'El Capitan' v10.11.6 (Build 15G21013)
- Xcode v8.2.1 (Build 8C1002)
- Homebrew v1.6.9
- Hardware and additional other configuration details available on request
- Reproduction configuration:
- macOS High Sierra (v10.13.5)
- Xcode v9.4
- Homebrew v1.6.9-27-g7db0f97 (From Git `master` branch, I believe.)- Original discovery configuration: - OS X 'El Capitan' v10.11.6 (Build 15G21013) - Xcode v8.2.1 (Build 8C1002) - Homebrew v1.6.9 - Hardware and additional other configuration details available on request - Reproduction configuration: - macOS High Sierra (v10.13.5) - Xcode v9.4 - Homebrew v1.6.9-27-g7db0f97 (From Git `master` branch, I believe.)
Description
As reported downstream to Homebrew by me in a comment on downstream issue #28455 and responded to by GitHub user 'apjanke' with a reply on that same issue's discussion thread and the creation of Homebrew issue #29415, building Qt's documentation fails when asked for on OS X/macOS during a build of Qt, either version 5.11.0 or 5.11.1, from source using said package manager.
In particular, this is because `qdoc` doesn't get build, apparently because, per further discussion in Homebrew issue #29415, your build system is having trouble finding Xcode's copy of `libclang` (at least under Homebrew, but possibly outside of that context, too.)
Homebrew has thus temporarily or permanently dropped support for building Qt's documentation locally (after failing to fix this issue by making Qt's build system use Homebrew's LLVM's `libclang` instead of Xcode's) as a result.
This is, however, obviously a regression, so it was suggested downstream that one of the individuals involved with this issue's counterpart there ask upstream for guidance on near-future directions with respect to handling it (thus my creation of this issue.)
Attachments
Issue Links
- duplicates
-
QTBUG-65762 Compiling qdoc in dev is a big pain
- Closed