Bug 413898 - Why has KDevelop Find{LLVM,Clang}.cmake instead of using their CMake modules?
Summary: Why has KDevelop Find{LLVM,Clang}.cmake instead of using their CMake modules?
Status: REPORTED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: git master
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: junior-jobs
Depends on:
Blocks:
 
Reported: 2019-11-07 00:04 UTC by Aaron Puchert
Modified: 2019-11-07 10:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Puchert 2019-11-07 00:04:42 UTC
Upstream LLVM/Clang provide CMake modules that provide all libraries as targets to link against, these are by default installed into <libdir>/cmake/{llvm,clang}/. They can also be used from a local LLVM/Clang build by setting LLVM_DIR=<build>/lib/cmake/llvm and Clang_DIR=<build>/lib/cmake/clang.

Why don't we use that instead of maintaining our own Find{LLVM,Clang}.cmake?
Comment 1 Kevin Funk 2019-11-07 10:21:10 UTC
The "Why?" is explained easily: The CMake config files for Clang have not been there when we started working with libclang.

I'm happy to switch to the CMake config files shipped by Clang once we're sure they actually work for us. 

So someone please try whether dissolving our Find{LLVM,Clang}.cmake is feasible and that the CMake config files shipped are usable.