[lldb-dev] [LLVMdev] [cfe-dev] LLVM 3.7 release plan and call for testers
hans at chromium.org
Thu Jun 25 10:02:14 PDT 2015
On Thu, Jun 25, 2015 at 9:01 AM, Ed Maste <emaste at freebsd.org> wrote:
> On 25 June 2015 at 09:34, Pavel Labath <labath at google.com> wrote:
>>>> For Clang and the main llvm libraries, we provide pre-built binaries
>>>> in the release, built with the utils/release/test-release.sh script. I
>>>> don't know if it would be practical to do this for lldb as well.
>>> We could, but I don't think there is nearly as much value in doing this for
>>> lldb as for clang/llvm.
>> I think having prebuilt binaries of lldb would be a good thing, as it
>> would make it much easier for people to try it out.
> Prebuilt Clang/LLVM binaries can be really useful for exploration
> since they might avoid a number of bootstrapping issues on new
> platforms. For end users looking to try out Clang/LLVM/LLDB I suspect
> they'll mostly just use packages provided by their OS, no? We'd also
> need to sort out packaging for the python bits etc. But I'm happy to
> build FreeBSD LLDB binaries (perhaps with python disabled?) if there's
> a desire.
I've never built lldb, so I don't really know what's involved and what
the "python bits" refer to. Would you or Pavel be willing to take a
look at llvm's utils/release/test-release.sh script and see what would
be necessary to teach that to package lldb based on some flag?
More information about the lldb-dev