]> granicus.if.org Git - clang/commit
Allow building libFuzzer in two-stage compiler-rt build
authorGeorge Karpenkov <ekarpenkov@apple.com>
Fri, 13 Oct 2017 22:03:09 +0000 (22:03 +0000)
committerGeorge Karpenkov <ekarpenkov@apple.com>
Fri, 13 Oct 2017 22:03:09 +0000 (22:03 +0000)
commitf9470527074c034b3f6da4b894416baf1c3998a7
tree17659d9ba41090c249b9bead6072ec9086cbb5da
parent8c0e12910379146b9e8a9d378435dc36bce158bd
Allow building libFuzzer in two-stage compiler-rt build

When LLVM_BUILD_EXTERNAL_COMPILER_RT option is set to true,
all of projects in compiler-rt are built with a freshly-built compiler using
a recursive CMake invocation.
(e.g. that's how compiler-rt is used in Swift)

Just now I have noticed that libFuzzer binaries were missing in such a case,
and ninja fuzzer returned "no such target", while ninja asan worked just fine.

To my surprise, the list of allowed targets was actually hardcoded in Clang!
While the current setup is clearly suboptimal, for the lack of a better fix
I'm just adding `fuzzer` to a list of `compiler-rt` targets.

Differential Revision: https://reviews.llvm.org/D38904

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@315771 91177308-0d34-0410-b5e6-96231b3b80d8
runtime/CMakeLists.txt