Even if building cxx_static in itself doesn't actually link in the
requested unwinder, add a synthetic dependency so that building
cxx_static makes sure that the unwinder that was requested to be used
also gets built.
Details
- Reviewers
ldionne - Group Reviewers
Restricted Project - Commits
- rGb1c9d3d29a1e: [libcxx] Add a dependency on unwind in cxx_static, if…
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
libcxx/src/CMakeLists.txt | ||
---|---|---|
289–294 | Should we put that dependency on check-cxx instead? We could add it to cxx-test-depends. |
libcxx/src/CMakeLists.txt | ||
---|---|---|
289–294 | That was my first idea, but in some sense, this felt more natural and symmetrical to adding the unwind dependency to cxx_shared right above here - so you get libunwind built if you have LIBCXXABI_USE_LLVM_UNWINDER set, when you do ninja cxx, even if you've only set up a static libcxx. But I don't feel strongly, I can post that version of the patch as well. |
Should we put that dependency on check-cxx instead? We could add it to cxx-test-depends.