<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I just went forward with this and made a quick test repo with an out-of-tree lldb-mi that compiles against the system LLDB: <a href="https://github.com/Teemperor/lldb-mi" class="">https://github.com/Teemperor/lldb-mi</a> This seems to work fine with the exception of the python tests which require LLDB’s python code for testing which isn’t installed alongside LLDB. I guess we will have to see if we copy the related test code there or we just rewrite the test suite (which is anyway broken). On the upside, we can now just use Travis for CI as we don’t have to compile LLVM/Clang/LLDB, so that’s nice.<div class=""><br class=""></div><div class="">I’m in favor of deprecating lldb-mi with 9.0.0 and then we can give downstream time until 10.0.0 (or X.0.0 :) ) to package out-of-tree lldb-mi for users. Given how simple lldb-mi is, this seems like a reasonable timeframe.</div><div class=""><div class=""><br class=""></div><div class=""><div class=""><div class="">- Raphael<br class=""><div class=""><br class=""></div><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Jul 4, 2019, at 9:51 AM, Davide Italiano via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 4, 2019 at 12:58 AM Zdenek Prikryl via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank" class="">lldb-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" class=""><p class="">We're using it with Eclipse and Eclipse based product, so I'd
like to keep as well! :-)...</p><p class="">Zdenek</p></div></blockquote><div class=""><br class=""></div><div class="">I do understand that there's desire from people to keep this around (from an user perspective), but I guess this fundamentally misses Jonas' original mail point.</div><div class="">lldb-mi has been unmaintained for a long time (at least the past two years from what I can tell), and we tried to use it in emacs without success.</div><div class="">It has never been a priority for many of the parties putting effort in lldb and I'm under the impression the situation won't change in the foreseeable future.</div><div class="">Unless somebody steps up as maintainer I don't think there's a lot of future for the tool. </div><div class="">Maybe a good compromise would be that of having lldb-mi living in a separate repo somewhere on GitHub, as it only uses the SBAPI, which is public and set in stone?</div><div class=""><br class=""></div><div class="">--</div><div class="">Davide</div></div></div>
_______________________________________________<br class="">lldb-dev mailing list<br class=""><a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev<br class=""></div></blockquote></div><br class=""></div></div></div></div></div></div></body></html>