bd1976bris wrote: > We use the multicall library. that is in fact our clang and lld (multicall is > basically like a busybox config). clang and lld exist in the build directory > and install as symlinks to the llvm binary. It's well supported in the CMake, > and has been used by us and others for several years now.
@ilovepi - thanks very much! I think that it is impossible in general for me to predict the name of the tool that will be returned by `ToolChain.getDriver().getClangProgramPath()` so I think that the fix to the test is trivial - I'll modify the Clang Driver test to simply check that there is a non-empty path supplied for the "--thinlto-remote-compiler" argument. We have the cross-project test which will check that the path is actually valid. https://github.com/llvm/llvm-project/pull/147265 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
