Can lldb-mi be placed into the llvm/tools directory and built with the rest ?

[mulle-nat]

That way "lldb-mi" would still be an optional download. It would work as before in terms of building it. Placing code into tools seems to be the llvm preferred way to build optional tools anyway, so the installation/build instructions could be even simpler. Just wondering...

[Teemperor]

I'm fine with this. In theory we only need to have some check if CMake is invoked on its own and then either use the old CMake or the current standalone one (which I believe is possible).

This will probably not be covered in CI though as compiling LLVM/Clang takes too long for a normal Travis job.

[ak-ambi]

Is it related to my problem?

lldb-mi was removed from the main source code and is no longer part of debian's lldb package since version 10.

The problem is that it was not added to any other pacakge. Should there be new package created? This tool is used by main C++ extension for VS code. It makes it impossible to debug using clang+vscode setup for clang 10 and newer.

[lalten]

I ran into the same problem as @ak-ambi on Arch, so I created a package at https://aur.archlinux.org/packages/lldb-mi-git/

[kgfly]

Eclipse CDT also uses lldb-mi for debugging. Currently, keeping it out of llvm project really cause lots of issue.

[shtirlic]

Opened KDE project in kdevelop and also it was requirement