walter-erquinigo wrote: A problem that I'm seeing now is that if we move all the plugins to `lldb_private::plugin`, the `liblldb-private.exports` file will by default emit all the lldb symbols (the ones in plugins + the regular lldb_private symbols). This can potentially be too many symbols, as IIUC some linkers have a limit for the number of symbols from exports files, like the windows linker. On the other hand, if the plugin symbols don't use the `lldb_private` namespace, we can leave `liblldb-private.exports` unchanged, and if someone wants the symbols of an specific plugin, they could just modify that file or provide their own. In other words, people could selectively pick the symbols of the plugins they want.
A workaround with sticking to the `lldb_private` namespace is to modify `liblldb-private.exports` to exclude in its regex `lldb_private::plugin` but to include any other `lldb_private`, and I don't really know if that would work with all linkers. So far I've just seen linkers using regexes without exclusions. https://github.com/llvm/llvm-project/pull/68150 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
