It's not just Apple that avoids GPL. Many LLVM users cannot use GPL. Adding GPL code to LLDB is a non-starter.
-- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project > -----Original Message----- > From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Jan > Kratochvil via lldb-dev > Sent: Wednesday, March 07, 2018 3:20 AM > To: William Schmidt <t.william.schm...@gmail.com> > Cc: lldb-dev@lists.llvm.org > Subject: Re: [lldb-dev] Command history line editing > > On Sun, 04 Mar 2018 21:03:26 +0100, William Schmidt via lldb-dev wrote: > > lldb deserves an editing mode functionally equivalent to what bash offers. > > And since bash is open-source, it should just be a matter of grabbing > > the bash source that implements command line editing and going from there. > > It is because lldb uses libedit while bash (and gdb) use readline. > > I guess it has licensing reasons as readline is GPL (not LGPL) and Apple > seems to > avoid GPL the family of licenses. IANAL but I think an alternative linking > with > readline while keeping the libedit compatibility still in place would not > taint > LLDB by the GPL license. And then OSes (such as Linux or for OSX is it > Homebrew?) already using GPL software could link LLDB with readline. > > > Jan > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
