Hi all,
What's the proper command line invocation to run our sources through to get
proper LLVM formatting and other desired fix-ups?
Thanks!
--
-Todd
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lld
Hi all,
I've taken a stab at getting the gtests in lldb/unittests to compile and
run on Xcode. I just checked this in. There's a new scheme called
lldb-gtest. If you run that in Xcode, it should build the DebugClang
variant of lldb and link against the gtest libraries that come with clang.
The
Okay this broke the cmake Linux build. I'm fixing that now...
On Sun, Oct 25, 2015 at 2:49 PM, Todd Fiala wrote:
> Hi all,
>
> I've taken a stab at getting the gtests in lldb/unittests to compile and
> run on Xcode. I just checked this in. There's a new scheme called
> lldb-gtest. If you run
This should be fixed with:
$ svn commit
unittests/Editline/CMakeLists.txt
Transmitting file data .
Committed revision 251264.
On Sun, Oct 25, 2015 at 2:55 PM, Todd Fiala wrote:
> Okay this broke the cmake Linux build. I'm fixing that now...
>
> On Sun, Oct 25, 2015 at 2:49 PM, Todd Fiala wrote
Hi Greg,
I tried using "_$" and "lldb$" as our private prefix, both of these solves the
issue and works fine for MIPS.
-Regards,
Bhushan
-Original Message-
From: Greg Clayton [mailto:gclay...@apple.com]
Sent: 23 October 2015 22:29
To: Bhushan Attarde
Cc: lldb-dev@lists.llvm.org
Subject