shafik added a comment. In D71306#1779379 <https://reviews.llvm.org/D71306#1779379>, @labath wrote:
> Besides lldb developers, another category we should consider are llvm (or > clang or lld, ...) developers who know nothing about lldb, but they ended up > building it because they specified LLVM_ENABLE_PROJECTS=all. These people > probably don't want to figure out how to install libedit, or how to disable > it, but if the default config "just works" for them, they'd be happy to build > lldb and make sure their patch doesn't break it. Optimizing for this > experience may be even more important than core lldb developers, since > there's fewer of the latter and they usually just configure lldb once. I want to seconded this, as someone who supports expression parsing which is depends on clang components which may be under active development such as `ASTImporter` having them being able to build lldb w/o a hassle is an important consideration if we want to them to be proactive and run the lldb test suite etc... Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D71306/new/ https://reviews.llvm.org/D71306 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
