[lldb-dev] Why do we support both configure and cmake generation?
ted.woodward at codeaurora.org
Fri Jan 23 11:35:52 PST 2015
Can LLDB really be built with python/swig using configure? I grepped for finishSwigWrapperClasses and finish-swig-wrapper-classes in all of llvm + clang + lldb, but only found references to finishSwigWrapperClasses in the lldb cmake files.
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
From: lldb-dev-bounces at cs.uiuc.edu [mailto:lldb-dev-bounces at cs.uiuc.edu] On Behalf Of Zachary Turner
Sent: Friday, January 23, 2015 12:58 PM
To: Vince Harron; lldb-dev at cs.uiuc.edu
Subject: Re: [lldb-dev] Why do we support both configure and cmake generation?
This is an issue on the LLVM side too. There's a master bug somewhere on the LLVM side tracking this, but the TL;DR is that CMake doesn't support everything (particularly when it comes to install) that the configure build supports. Most of the interested players that I'm aware of have said they won't mind dropping Make in favor of CMake once those issues are taken care of. But FWIU they're not easy.
On Fri Jan 23 2015 at 10:50:25 AM Vince Harron <vharron at google.com <mailto:vharron at google.com> > wrote:
We're having a problem right now where the buildbot (which uses configure) is working but we're unable to build locally with cmake. We're investigating the cmake problem now.
The question is, if we have CMake files (which can generate ninja or make among others) Why do we still have configure/make?
Vince Harron |
Technical Lead Manager |
vharron at google.com <mailto:vharron at google.com> |
lldb-dev mailing list
lldb-dev at cs.uiuc.edu <mailto:lldb-dev at cs.uiuc.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev