jingham requested changes to this revision. jingham added a comment. I agree with Greg, I really don't want to lose the "lldb -P" functionality. That's quite handy.
Seems to me that if lldb wants to provide a scripting module for some scripting language, that language would need to know where the module lived in order to load it. So having a generic "Get the lldb module location" API to help users do that automatically seems entirely appropriate. Just call it GetLLDBScriptingModuleDir or something and I think that would make total sense. Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D61090/new/ https://reviews.llvm.org/D61090 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
