configuring qt-everywhere-src-6.5.2 gives llvm and clang error
-
I want to install qt 6.5.2 on windows 10 for visual studio 2019.
I am trying to configure qt-everywhere-src-6.5.2 using x64 Visual Studio 2019 Command Prompt.
I ran configure.bat where it gave many dependencies error which I resolved. Now configuration is stuck up at LLVM and clang.*WARNING: QDoc will not be compiled, probably because libclang could not be located. This means that you cannot build the Qt documentation. **Either set CMAKE_PREFIX_PATH or LLVM_INSTALL_DIR to the location of your llvm installation.** On Linux systems, you may be able to install libclang by installing the libclang-dev or libclang-devel package, depending on your distribution. On macOS, you can use Homebrew's llvm package. You will also need to set the FEATURE_clang CMake variable to ON to re-evaluate this check. **WARNING: Clang-based lupdate parser will not be available. LLVM and Clang C++ libraries have not been found.** You will need to set the FEATURE_clangcpp CMake variable to ON to re-evaluate this check.*
I have installed LLVM-16.0.4-win64.exe from https://github.com/llvm/llvm-project/releases/tag/llvmorg-16.0.4. C:\Program Files\LLVM\bin; path is also present in PATH env variable. But still I get above error.
How to resolve this issue?
-
@RkTest said in configuring qt-everywhere-src-6.5.2 gives llvm and clang error:
How to resolve this issue?
Why do you need QDoc at all? What do you want to debug in qdoc that you need to compile it from source?
-
The binaries from llvm.org do not include the CMake package files that Qt looks after.
See https://lists.qt-project.org/pipermail/development/2023-August/044284.html for more details.
You either build LLVM yourself statically or you take precompiled binaries from https://download.qt.io/development_releases/prebuilt/libclang/qt/ but there can be other issues. See the mailing list thread for the nitty gritty details.
-
@Christian-Ehrlicher Thanks for your reply. I dont need qdoc. But will this error/warning affect the building?
-
@cristian-adam Thank you. I will try it.