[libcxx-commits] [libcxx] [libc++] Introduce ABI sensitive areas to avoid requiring _LIBCPP_HIDE_FROM_ABI everywhere (PR #131156)
Derek Schuff via libcxx-commits
libcxx-commits at lists.llvm.org
Tue May 20 16:53:12 PDT 2025
dschuff wrote:
We can maybe work around this.
However the use case here is not a typical library use case of "create a DSO with a public API for re-use across different projects" (in which I totally agree that you want to use hidden visibility and explicit exports). Instead it's just to share a bunch of code between several related tools which are all shipped together as part of a single implementation and package; the real goal is to minimize distribution size. The DSO is just a private implementation detail, so really we want to export everything. But I don't see a good way to do that (other than marking every function with visibility attributes, which is invasive and error-prone). I suspect this use case is more common that you seem to be assuming here.
https://github.com/llvm/llvm-project/pull/131156
More information about the libcxx-commits
mailing list