[lldb-dev] [Bug 28953] New: Xcode build: be explicit about which clang and LLVM .a files get linked into LLDB

via lldb-dev lldb-dev at lists.llvm.org
Fri Aug 12 09:57:46 PDT 2016


            Bug ID: 28953
           Summary: Xcode build: be explicit about which clang and LLVM .a
                    files get linked into LLDB
           Product: lldb
           Version: unspecified
          Hardware: PC
                OS: MacOS X
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: lldb-dev at lists.llvm.org
          Reporter: todd.fiala at gmail.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

The Xcode build uses the scripts/Xcode/build-llvm.py script.  That script makes
a simplification to link against LLVM and clang libs, simply linking against
all the .a files.

While this is simple, it also is not accurate.  Incremental builders can run
into trouble if a library gets refactored into another, in which case we'll
still link against the stale, inert .a files that were orphaned, leading to
whatever linkage issues that may entail.

In addition, we are potentially increasing the amount of work the linker needs
to do to cut out dead code.

Change the script to be explicit about what we need to link against within LLVM
and clang.  This may require some investigation on the clang side.  See
comments here:


Those comments indicate we may be able to use llvm-config for the LLVM side.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20160812/5b5a0cc5/attachment-0001.html>

More information about the lldb-dev mailing list