[lldb-dev] [OS X]: building lldb with cmake

[René J.V. Bertin via lldb-dev]

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 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 even sure where to start. So far I'm focusing
>on the other LLVM components but I should be able to get to LLDB soon.
>Though I can't promise much since my time is quite limited.

There really isn't much to be done to get it to work, esp. if the abovementioned class is already removed:

- fix finding CheckAtomic.cmake (or just install it with LLVM)
- fix the install location as recorded in liblldb and make sure that location gets added to the rpath in lldb, lldb-mi and other dependents.

There's also an issue finding the proper Python library, at least when building MacPorts. It finds the correct framework binary when doing a complete build using the toplevel CMake file, but apparently goes for the latest version if you use the standalone build.

R.