diff options
| author | Reid Kleckner <rnk@google.com> | 2019-09-12 18:44:47 +0000 |
|---|---|---|
| committer | Reid Kleckner <rnk@google.com> | 2019-09-12 18:44:47 +0000 |
| commit | 0e88ebe11d930a2c8c1433ffbf0e345b0fb7bef7 (patch) | |
| tree | d8dfce07703d56d507eb9ab84f4d5eb532d7146b /clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp | |
| parent | b6a8152b8bf7dc7b56e2953575037281af3d9133 (diff) | |
| download | llvm-0e88ebe11d930a2c8c1433ffbf0e345b0fb7bef7.zip llvm-0e88ebe11d930a2c8c1433ffbf0e345b0fb7bef7.tar.gz llvm-0e88ebe11d930a2c8c1433ffbf0e345b0fb7bef7.tar.bz2 | |
Use host's executable suffix for clang when cross-compiling compiler-rt
When cross-compiling compiler-rt as part of LLVM e. g. for Linux on
a Windows host and using the just-built clang as cross-compiler, we set
the -DBUILTINS_CMAKE_ARGS="-DCMAKE_SYSTEM_NAME=Linux" flag in top-level
cmake invocation, which causes CMAKE_EXECUTABLE_SUFFIX to be an empty
string in the nested cmake invocation for building builtins.
But the compiler for compiling test cases is meant to be run on host,
therefore it may have the '.exe' suffix.
Handle this by asking cmake about the host system.
Patch by Sergej Jaskiewicz <jaskiewiczs@icloud.com>
Reviewed By: rnk
Differential Revision: https://reviews.llvm.org/D67401
llvm-svn: 371754
Diffstat (limited to 'clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions