On Saturday September 10 2016 17:26:26 Michał Górny wrote:
Re: MIUtilParse: I'm building the 3.9.0 release so no worries that the class
has been added back supposing it was removed *after* the release.
>> Agree that a standalone build would be great to have working, it just
>> requires someone w
On Sat, 10 Sep 2016 15:09:13 +
Zachary Turner via lldb-dev wrote:
> Agree that a standalone build would be great to have working, it just
> requires someone willing and able to come along and fix it :)
I have it on my TODO but honestly speaking, LLDB is a bit of a mess
right now and I'm not
On Fri, 09 Sep 2016 12:37:01 -0700 (PDT)
René J.V. Bertin via lldb-dev wrote:
> Hi,
>
> I wanted to see how far I could get with a standalone build, so I copied the
> missing CheckAtomic.cmake file into the installed cmake/llvm directory, and
> tried to build lldb.
> It aborted at 93% because
Agree that a standalone build would be great to have working, it just
requires someone willing and able to come along and fix it :)
On Sat, Sep 10, 2016 at 1:00 AM René J.V. Bertin
wrote:
> On Friday September 09 2016 20:00:34 Zachary Turner wrote:
> >To be completely honest with you I don't eve
There's another issue with the standalone build.
I call cmake with -DDCMAKE_INSTALL_PREFIX=/opt/local/libexec/llvm-3.9, so that
lldb gets installed with the rest of llvm 3.9, into /opt/local/libexec/llvm-3.9
. It looks like liblldb.${version} is generated with the wrong install path
recorded:
On Friday September 09 2016 20:00:34 Zachary Turner wrote:
>To be completely honest with you I don't even know why this class exists.
>All it needs to do is use llvm's regex class. The entire MIUtilParse.h /
>.cpp files can be deleted as far as I'm concerned.
That clearly needs a bit more work, i
