HighCommander4 wrote: The name of the existing `detectClangPath()` function is a bit misleading, because [one of things it might return](https://searchfox.org/llvm/rev/f21080724d2067b5acf01893bf2d544b49239161/clang-tools-extra/clangd/CompileCommands.cpp#107-108) is a `gcc` or `cc` executable found on the PATH (`detectCompilerPath()` would be a more accurate name).
In these cases, looking for a resource directory based on that path doesn't make much sense... but I guess it will just fail to find one, so it seems harmless. https://github.com/llvm/llvm-project/pull/203332 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
