This is the same way that libc++abi static linking is handled in libc++.
Resolves PR45348.
Differential D77296
[libc++abi] Make libunwind static linking possible in standalone builds tambre on Apr 2 2020, 5:22 AM. Authored by
Details
This is the same way that libc++abi static linking is handled in libc++. Resolves PR45348.
Diff Detail
Event TimelineComment Actions I think that @ldionne should chime in on this change. Mechanically, sure, I don't see any problems with the change.
Comment Actions Add cache variable for LIBCXXABI_UNWIND_LIBRARY_PATH to improve discoverability and clarify usage.
Comment Actions Could you please chime in on http://lists.llvm.org/pipermail/libcxx-dev/2020-April/000793.html? I'd like to better understand why we even need to support a standalone build -- I thought we were not supporting those anymore since the monorepo. Comment Actions I'll chime in on that. I just recently migrated the company I work for to LLVM, so I was only aware that building in a non-monorepo layout is unsupported now. Comment Actions ldionne: Ping. Per the mailing list thread it seems reasonable to support this scenario. Comment Actions ldionne: ping. From what I gather, building projects separately is still supported, but I remain unaware of an option to accomplish what I want without downsides. I'd really rather not keep a single out-of-tree patch for my use. |
Where is LIBCXXABI_UNWIND_LIBRARY_PATH defined? I can't find that CMake option anywhere.