Unfortunately, the LLDB we build needs to run on SLES 11, Ubuntu 10+ and who knows what else. I don’t think I can require they install a six package. I can make our build do a copy instead of a link, if you want to keep it a link.
Are the static swig bindings checked in yet, or do we still need to run swig to generate them on each build? -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project From: Zachary Turner [mailto:ztur...@google.com] Sent: Wednesday, December 09, 2015 3:47 PM To: Ted Woodward; LLDB Subject: Re: [lldb-dev] swig generation and "six" module What about requiring that the user has done "pip install six" on their machine? On Wed, Dec 9, 2015 at 1:40 PM Ted Woodward via lldb-dev <lldb-dev@lists.llvm.org <mailto:lldb-dev@lists.llvm.org> > wrote: r252764 changes finishSwigPythonLLDB.py to symlink the “six” module in site-packages. six.py is a symlink to <llvm>/tools/lldb/third_party/Python/module/six/six.py. This assumes I have access to this build’s sources when I run lldb, which I don’t – our workstations don’t have access to the buildbots’ filesystem, and even if they did, the sources may change between build and run. Shouldn’t six.py just be copied? It’s only 30k. Zach, how do I do a build using static swig bindings? I don’t think we’re going to change the bindings internally, so using the standard ones should be fine. -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org <mailto: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
