[Lldb-commits] [PATCH] Don't try to link against a release python during a debug build.

Todd Fiala tfiala at google.com
Thu Jul 10 11:00:51 PDT 2014

> We can try to streamline this in the future by checking in a hermetic
copy of Python with necessary build files, but until that day comes,
building manually seems like the best option.  Note that this only applies
if you have LLDB_DISABLE_PYTHON=0, which is NOT the default.

FWIW this is highly unlikely to happen due to the purity of license that
LLVM wants to adhere to - we have way too many organizations using
LLVM-based code to want to pollute the license in any way.

I'll have a look at the patch as soon as I get a few cycles. Should be

On Wed, Jul 9, 2014 at 3:36 PM, Zachary Turner <zturner at google.com> wrote:

> Stop normalizing the case of .py files when they're copied over.  Python
> module names are case-sensitive, so this can lead to errors.
> http://reviews.llvm.org/D4441
> Files:
>   CMakeLists.txt
>   include/lldb/lldb-python.h
>   scripts/Python/finishSwigPythonLLDB.py

Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20140710/36735322/attachment.html>

More information about the lldb-commits mailing list