The Hexagon toolchain uses “hexagon-“ as a program prefix, so we distribute hexagon-lldb, hexagon-clang, hexagon-llvm-mc, etc. RPATH is $(ORIGIN)/../lib, so lldb picks up liblldb.so from the Hexagon tools lib directory.
.lldbinit would be shared, but if you named your lldb “android-lldb”, it would load ~/.lldbinit-android-lldb (or /users/<name>/AppData/Roaming/.lldbinit-android-lldb.exe on Windows, which needs to be fixed to remove the .exe). -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project From: lldb-dev-boun...@cs.uiuc.edu [mailto:lldb-dev-boun...@cs.uiuc.edu] On Behalf Of Vince Harron Sent: Saturday, May 16, 2015 11:08 AM To: lldb-dev@cs.uiuc.edu Subject: [lldb-dev] Distributing a second lldb on OS X Hi Greg/all, Pretty soon, we are going to want to start distributing lldb for use with Android targets. It will be distributed as part of our SDK and will very likely be installed on a machine that also has Xcode. We don't want the two lldb installations to interfere with each other. I don't anticipate this being a problem but I wanted to raise the issue to get your thoughts. Thanks, Vince
_______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
