I have created this change as a way to solicit feedback and foster
discussion. My goal is to sever lldbTarget's dependence on
lldbPluginProcessUtility as a part of my larger goal of more cleanly
setting boundaries between lldb's core libraries and lldb's plugin
libraries.
For the purposes of concretely demonstrating what severing the
dependence would look like, I made the easiest change possible (moving
files). I don't think this is the right kind of change because
lldbTarget should ideally be platform-independent. I considered turning
UnixSignals into a Plugin, but to me this felt like overkill. I think
the best change may be somewhere else (possibly creating a new non-plugin
library?) but I'm not sure what that should look like.
Feedback is appreciated.
clang-tidy: error: 'Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.h' file not found [clang-diagnostic-error]
not useful
clang-tidy: error: 'Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.h' file not found [clang-diagnostic-error]
not useful