Re: [lldb-dev] LLDB C++ API integration.

2017-08-08 Thread Jim Ingham via lldb-dev
> On Aug 7, 2017, at 9:15 PM, Mikhail Seriukov wrote: > > Hi Jim, thank you for your response! > > If I choose to build the framework, there is a code signing problem. > For the debugserver (and lldb-server?) we need lldb_codesign certificate. > I was wondering if I could use my Mac developer

Re: [lldb-dev] LLDB C++ API integration.

2017-08-07 Thread Mikhail Seriukov via lldb-dev
Hi Jim, thank you for your response! If I choose to build the framework, there is a code signing problem. For the debugserver (and lldb-server?) we need lldb_codesign certificate. I was wondering if I could use my Mac developer certificate instead? Also I've found the DEBUGSERVER_USE_FROM_SYSTEM

Re: [lldb-dev] LLDB C++ API integration.

2017-08-07 Thread Jim Ingham via lldb-dev
One of the rules of the SB API's both on the Python & C++ side is that we maintain backwards compatibility (up to some time in the Future when we'll declare a SB 2.0...) So if you compile your tool against some version of the framework, you should be able to run against any newer version. Apple

[lldb-dev] LLDB C++ API integration.

2017-08-06 Thread Mikhail Seriukov via lldb-dev
Hi, I want to write a Mac app that uses LLDB C++ API. What is the best way to do it? Should I build and codesign the framework myself, how can I distribute it then? Should I reuse the framework from "Command line tools", but then I should force users to install it? How should I structure my Xcode