[lldb-dev] [RFC] Removing lldb-mi

[Nat! via lldb-dev]

I was asked by the author of lldb-mi, to forward this to the list, since 
he is not subscribed:

Illya Rudkin schrieb am 05.07.19 um 10:37:
> Hi Nat
> 
> Thank you for bring this to my attention. Yes I am the original author 
> but for a long time now I have not been involved in its further 
> development or maintenance. I have been popping in to the Git repository 
> occasionally to see the activity and it seems to me there are people 
> actively maintaining to this day, either fixing commands or adding new 
> ones. This is not very often mind perhaps indicating its maturity. Of 
> course this does not indicate the number of people actively using it 
> today or how they access the tool to use it, Eclipse users being main 
> ones in the past. I am not sure how to get this information.
> 
> (To the others in this discussion) Anyway to the point of the this 
> discussion I do not mind if it stays where it is currently or is moved. 
> The thing I would say is just remember even if you may not be using it 
> or interested in it there may be others who are. It may be a bit of 
> noise for you but it is a dependency for them. Perhaps reach out before 
> making a decision.
> 
> All the best
> 
> Illya
> 
> *From: *Nat! <nat at mulle-kybernetik.com>
> *Date: *Thursday, 4 July 2019 at 22:21
> *To: *Illya Rudkin <illya at codeplay.com>
> *Subject: *Fwd: Re: [lldb-dev] [RFC] Removing lldb-mi
> 
> Hi
> 
> I am forwarding you this, because I believe you are the original author 
> of lldb-mi. I think I prefer, if it would stay in the project, but I am 
> not really sure.
> 
> Ciao
>     Nat!
> 
> 
> -------- Forwarded Message --------
> 
> *Subject: *
> 
> 	
> 
> Re: [lldb-dev] [RFC] Removing lldb-mi
> 
> *Date: *
> 
> 	
> 
> Thu, 4 Jul 2019 12:24:48 -0700
> 
> *From: *
> 
> 	
> 
> Raphael “Teemperor” Isemann via lldb-dev <lldb-dev at lists.llvm.org> 
> <mailto:lldb-dev at lists.llvm.org>
> 
> *Reply-To: *
> 
> 	
> 
> Raphael “Teemperor” Isemann <teemperor at gmail.com> 
> <mailto:teemperor at gmail.com>
> 
> *To: *
> 
> 	
> 
> Davide Italiano <dccitaliano at gmail.com> <mailto:dccitaliano at gmail.com>
> 
> *CC: *
> 
> 	
> 
> LLDB <lldb-dev at lists.llvm.org> <mailto:lldb-dev at lists.llvm.org>
> 
> 
> 
> 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: 
> https://github.com/Teemperor/lldb-mi 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.
> 
> 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.
> 
> - Raphael
> 
>     On Jul 4, 2019, at 9:51 AM, Davide Italiano via lldb-dev
>     <lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org>> wrote:
> 
>     On Thu, Jul 4, 2019 at 12:58 AM Zdenek Prikryl via lldb-dev
>     <lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org>> wrote:
> 
>         We're using it with Eclipse and Eclipse based product, so I'd
>         like to keep as well! :-)...
> 
>         Zdenek
> 
>     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.
> 
>     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.
> 
>     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.
> 
>     Unless somebody steps up as maintainer I don't think there's a lot
>     of future for the tool.
> 
>     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?
> 
>     --
> 
>     Davide
> 
>     _______________________________________________
>     lldb-dev mailing list
>     lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org>
>     https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>