This gains us the install-unwind-stripped target, to perform stripping
during installation.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
Hmm, this change means very recent LLVM is required to build libunwind-- previously I was able to use recent libunwind/libcxx/libcxxabi with LLVM 5 and LLVM 4.
Other runtime projects (compiler-rt, libcxx, libcxxabi) were modified to support the new "strip-and-install" targets such that they didn't depend on LLVM cmake bits, could that sort of approach work here?
The other runtime projects had the stripped installation targets added manually because they officially support being built completely standalone (i.e. without any LLVM components), so we can't rely on LLVM's CMake there. That's really unfortunate IMO, since it leads to a bunch of duplication, but it is what it is.
libunwind doesn't support building completely standalone AFAIK, so I think assuming trunk libunwind will be paired with trunk LLVM is pretty reasonable in general. It's easy enough to not break your use case here, however, so I went ahead and did so in r320163.