tree 662ea3377df886c794ddf3b6226199502269d0e4
parent 91c593a0e275cfd03ef2ea353013316547f0ad7c
author George Karpenkov <ekarpenkov@apple.com> 1507932189 +0000
committer George Karpenkov <ekarpenkov@apple.com> 1507932457 -0700

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
(cherry picked from commit f9470527074c034b3f6da4b894416baf1c3998a7)