[lldb-dev] LLDB back in sync with top-of-tree LLVM/Clang

[NAKAMURA Takumi]

2012/9/25 João Matos <ripzonetriton at gmail.com>:
> Could we get a MSVC build bot of the Windows branch too? If this is possible
> who should I contact?

I may maintain a builder in bb.pgr.jp, when the build (of lldb) would be ready.

Then, I assume lldb should be in sync against llvm (and clang) trunk.

> On Tue, Sep 25, 2012 at 11:30 AM, NAKAMURA Takumi <geek4civic at gmail.com>
> wrote:
>>
>> George, as far as I know,
>>
>> http://lab.llvm.org:8011/builders/lldb-x86_64-linux
>> http://llvm-amd64.freebsd.your.org:8010/builders/lldb-amd64-freebsd
>> http://llvm-amd64.freebsd.your.org:8010/builders/lldb-i386-freebsd
>>
>> ...Takumi
>>
>> 2012/9/25 George Russell <george at codeplay.com>:
>> > Hi,
>> >
>> > Are there currently any publically viewable LLDB build-bots that can
>> > show
>> > the build status / test status of LLDB?
>> >
>> > Cheers,
>> > George
>> >
>> >
>> > On 25/09/12 00:23, Sean Callanan wrote:
>> >>
>> >> As of revision 164563 (but, as I say below, please check out 164573),
>> >> LLDB
>> >> is back in sync with top-of-tree Clang.
>> >>
>> >> This commit has several important implications:
>> >> –
>> >> 1. LLDB is no longer tied to a specific Clang revision.  LLDB
>> >> top-of-tree
>> >> is intended to build against Clang top-of-tree.  That means we have to
>> >> fix
>> >> any build failures quickly, and I'll be keeping track of compatibility
>> >> until
>> >> we get a more permanent solution.
>> >> 2. We no longer use local patches (scripts/{llvm,clang}.*.diff) of any
>> >> sort.  To ensure LLDB stability, we will make LLDB release branches
>> >> that
>> >> will be tied to Clang release branches.
>> >> 3. We no longer use or commit llvm.zip.  If you don't want to have to
>> >> rebuild Clang, just don't update your local lldb/llvm tree.
>> >> –
>> >> Building LLDB on OS X works the same way it did before: open up
>> >> lldb.xcworkspace and build the LLDB scheme.
>> >>
>> >> For your convenience, I have added a new configuration to the
>> >> .xcodeproj:
>> >> DebugClang (available as of revision 164573).  Here's the difference
>> >> between
>> >> Debug and DebugClang:
>> >>
>> >> - Debug builds a Release+Asserts version of Clang, which is easy on the
>> >> debug information size, but still appropriately yelps when LLDB abuses
>> >> it.
>> >> - DebugClang builds a Debug+Asserts version of Clang, which contains a
>> >> TON
>> >> of debug information.
>> >>
>> >> Unless you are working specifically on the Clang integration, you'll
>> >> probably prefer Debug.
>> >>
>> >> Sean
>> >> _______________________________________________
>> >> lldb-dev mailing list
>> >> lldb-dev at cs.uiuc.edu
>> >> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>> >
>> >
>> > _______________________________________________
>> > lldb-dev mailing list
>> > lldb-dev at cs.uiuc.edu
>> > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>>
>> _______________________________________________
>> lldb-dev mailing list
>> lldb-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
>
>
>
> --
> João Matos