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.<br><br>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.<br><br>With that in mind, thoughts on moving everything to Utility?<br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 20, 2017 at 5:56 AM Pavel Labath via Phabricator <<a href="mailto:reviews@reviews.llvm.org">reviews@reviews.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">labath created this revision.<br>
Herald added a subscriber: mgorny.<br>
<br>
All implementations of the connection interface live in the Host module<br>
already, so it makes sense for the interface itself to be defined there.<br>
<br>
<br>
<a href="https://reviews.llvm.org/D34400" rel="noreferrer" target="_blank">https://reviews.llvm.org/D34400</a><br>
<br>
Files:<br>
  include/lldb/Core/Connection.h<br>
  include/lldb/Host/Connection.h<br>
  include/lldb/Host/posix/ConnectionFileDescriptorPosix.h<br>
  include/lldb/Host/windows/ConnectionGenericFileWindows.h<br>
  source/Core/CMakeLists.txt<br>
  source/Core/Communication.cpp<br>
  source/Core/Connection.cpp<br>
  source/Host/CMakeLists.txt<br>
  source/Host/common/Connection.cpp<br>
  source/Host/posix/ConnectionFileDescriptorPosix.cpp<br>
  tools/lldb-server/Acceptor.h<br>
<br>
</blockquote></div>