etcwilde wrote: > We can't really help you with whatever is wrong with Debian's packages unless > it is a bug caused by our build configurations. The change you're proposing > in this PR could just as easily be impacted in some distro's packages.
The exported target is new and hasn't been in a release yet. It should be in LLVM-19 once it's released and Debian gets updated. Of course, this is also true of any other new thing that gets added now anyway. I am a little confused about what your goal is with the path manipulations though. The part of IWYU that is [linked](https://github.com/include-what-you-use/include-what-you-use/blob/master/CMakeLists.txt#L54) above is looking for the `clang-resource-headers` target if one exists, or trying to find the include directory. I'm not familiar with how IWYU works either though. It kind of looks like it's embedding a copy of clang (sort of like how Swift does), in which case, it should embed the resource headers that match that clang and you should know where you're installing them. If that's not the case and it's invoking `clang` somewhere, then passing `-print-resource-dir` to that clang will give you the resource directory, and then the headers are under the `include` directory there. But in both cases, from what I can tell, you're asking about where the headers are, which is what the `clang-resource-headers` target contains. What other bits are you looking for in the resource directory? https://github.com/llvm/llvm-project/pull/97197 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
