xiaobai added a comment. In D58193#1398376 <https://reviews.llvm.org/D58193#1398376>, @labath wrote:
> BTW, what's the reason for having super-high-fidelity list of dependencies in > a standalone build? I know that they're important for in-tree builds, as that > makes sure everything is built when you run "check-lldb". However, that's > isn't going to help you with standalone builds. The binaries are already > there, or they aren't, and there's nothing we can do to change that. I'd > consider just removing all non-lldb targets from the deps list when in > standalone mode. I think it's useful to be able to fully test lldb if you have all the available tools even if it's built standalone. This is especially relevant for swift-lldb, which more often than not is built standalone because swift is often built standalone. I'm generally not in favor of keeping things around only because somebody downstream uses it, but I can see the usefulness for people who work on upstream LLDB as well. I'm not sure if other people feel the same way though. Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D58193/new/ https://reviews.llvm.org/D58193 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
