I had actually been considering going the other way. Moving connection and all implementations to Utility. Host is a big contributor to the dependency problems, so putting more stuff in seems like the wrong direction.
The end state i had in mind was similar to llvm support (which is more less the equivalent of lldb host), where it has all the host specific functionality but contains no deps. With that in mind, thoughts on moving everything to Utility? On Tue, Jun 20, 2017 at 5:56 AM Pavel Labath via Phabricator < revi...@reviews.llvm.org> wrote: > labath created this revision. > Herald added a subscriber: mgorny. > > All implementations of the connection interface live in the Host module > already, so it makes sense for the interface itself to be defined there. > > > https://reviews.llvm.org/D34400 > > Files: > include/lldb/Core/Connection.h > include/lldb/Host/Connection.h > include/lldb/Host/posix/ConnectionFileDescriptorPosix.h > include/lldb/Host/windows/ConnectionGenericFileWindows.h > source/Core/CMakeLists.txt > source/Core/Communication.cpp > source/Core/Connection.cpp > source/Host/CMakeLists.txt > source/Host/common/Connection.cpp > source/Host/posix/ConnectionFileDescriptorPosix.cpp > tools/lldb-server/Acceptor.h > >
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
