clayborg wrote: I didn't realize there was already a cmake option for exporting the lldb_private namespace when I made my first comments. For this option to truly be useful, I would prefer to have a liblldb_private.so/LLDBPrivate.framework that we would create and then have the liblldb.so/LLDB.framework link against these libraries. We went through great lengths to ensure that we vend a backward compatible API from liblldb.so/LLDB.framework and I would like to keep it that way. If nothing from lldb_private or other internal APIs are exported by enabling a special cmake config variable, then we should only have liblldb.so/LLDB.framework with a backward compatible API. If we enable a flag that exports unsafe APIs we have both a liblldb.so/LLDB.framework whichs links to the unsafe API libraries liblldb_private.so/LLDBPrivate.framework.
https://github.com/llvm/llvm-project/pull/67851 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
