Re: [lldb-dev] lldb-mi has been moved to its own GitHub repository

2019-08-13 Thread Raphael Isemann via lldb-dev 
Agreed, I made a PR (which is work in progress):
https://github.com/lldb-tools/lldb-mi/pull/5 (I didn't try compiling
against a compiled LLDB, so that is subject to change).

Am Di., 13. Aug. 2019 um 19:29 Uhr schrieb Ted Woodward :
>
> The build instructions in README.md are a tad sparse:
>
> Build
>
> cmake . ; cmake --build .
>
>
>
>
>
> Where do we put it in relation to an lldb build?
>
> Does it need the llvm/lldb sources?
>
> Is it built against an lldb build, or an lldb install?
>
>
>
> Ted
>
>
>
> From: lldb-dev  On Behalf Of Raphael 
> “Teemperor” Isemann via lldb-dev
> Sent: Tuesday, August 13, 2019 3:18 AM
> To: LLDB 
> Subject: [EXT] [lldb-dev] lldb-mi has been moved to its own GitHub repository
>
>
>
> Hi all,
>
> lldb-mi has been moved out of the LLDB source tree into its own GitHub 
> repository here: https://github.com/lldb-tools/lldb-mi lldb-mi is now a 
> standalone tool that builds against LLDB, but is no longer build as part of 
> LLDB. The implications for users are:
>
> 1. Package maintainers need to package lldb-mi and no longer receive the 
> lldb-mi executable as a side product of LLDB. The lldb-mi build system is 
> very simple, so I don’t expect a lot of problems arising from this change. 
> Note: You can *NOT* drop in the lldb-mi source into the old folder inside the 
> LLDB source tree. You need to first build LLDB and then build lldb-mi against 
> it.
>
> 2. If you encounter bugs with lldb-mi, please file a report on the GitHub 
> project and *NOT* on the LLVM bugzilla. We closed all lldb-mi bugs on 
> bugzilla, so if you think your issue with lldb-mi still exists, please copy 
> your bug report to GitHub.
>
>
>
> In other news: lldb-mi is also in need of a maintainer!
>
>
>
> The good thing is that with this change lldb-mi you can now make pull 
> requests against the project, we set up a CI system and in general its easier 
> to get started with lldb-mi. Note that during the move lldb-mi lost its test 
> suit, meaning that there are currently no tests run in the CI. This was 
> mostly because we couldn’t port over the old test suit (which depended on the 
> internal LLDB python test suit) and because most of the tests we had were 
> anyway disabled due to random failures. If you want to get started, feel free 
> to make pull requests with tests (preferable more reliable than the old ones 
> we had).
>
>
>
> I’m mostly writing this as the change was buried in the RFC thread last month 
> and it seems all downstream folks are still completely unaware this.
>
>
>
> TL;DR: LLDB no longer provides the lldb-mi executable. You now need to 
> get lldb-mi from the GitHub repository above.
>
>
>
> Cheers,
>
> - Raphael
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-mi has been moved to its own GitHub repository

2019-08-13 Thread Ted Woodward via lldb-dev 
The build instructions in README.md are a tad sparse:
Build
cmake . ; cmake --build .


Where do we put it in relation to an lldb build?
Does it need the llvm/lldb sources?
Is it built against an lldb build, or an lldb install?

Ted

From: lldb-dev  On Behalf Of Raphael 
“Teemperor” Isemann via lldb-dev
Sent: Tuesday, August 13, 2019 3:18 AM
To: LLDB 
Subject: [EXT] [lldb-dev] lldb-mi has been moved to its own GitHub repository

Hi all,

lldb-mi has been moved out of the LLDB source tree into its own GitHub 
repository here: https://github.com/lldb-tools/lldb-mi lldb-mi is now a 
standalone tool that builds against LLDB, but is no longer build as part of 
LLDB. The implications for users are:

1. Package maintainers need to package lldb-mi and no longer receive the 
lldb-mi executable as a side product of LLDB. The lldb-mi build system is very 
simple, so I don’t expect a lot of problems arising from this change. Note: You 
can *NOT* drop in the lldb-mi source into the old folder inside the LLDB source 
tree. You need to first build LLDB and then build lldb-mi against it.

2. If you encounter bugs with lldb-mi, please file a report on the GitHub 
project and *NOT* on the LLVM bugzilla. We closed all lldb-mi bugs on bugzilla, 
so if you think your issue with lldb-mi still exists, please copy your bug 
report to GitHub.

In other news: lldb-mi is also in need of a maintainer!

The good thing is that with this change lldb-mi you can now make pull requests 
against the project, we set up a CI system and in general its easier to get 
started with lldb-mi. Note that during the move lldb-mi lost its test suit, 
meaning that there are currently no tests run in the CI. This was mostly 
because we couldn’t port over the old test suit (which depended on the internal 
LLDB python test suit) and because most of the tests we had were anyway 
disabled due to random failures. If you want to get started, feel free to make 
pull requests with tests (preferable more reliable than the old ones we had).

I’m mostly writing this as the change was buried in the RFC thread last month 
and it seems all downstream folks are still completely unaware this.

TL;DR: LLDB no longer provides the lldb-mi executable. You now need to 
get lldb-mi from the GitHub repository above.

Cheers,
- Raphael

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] lldb-mi has been moved to its own GitHub repository

2019-08-13 Thread Raphael “Teemperor” Isemann via lldb-dev 
Hi all,

lldb-mi has been moved out of the LLDB source tree into its own GitHub 
repository here: https://github.com/lldb-tools/lldb-mi 
 lldb-mi is now a standalone tool that 
builds against LLDB, but is no longer build as part of LLDB. The implications 
for users are:

1. Package maintainers need to package lldb-mi and no longer receive the 
lldb-mi executable as a side product of LLDB. The lldb-mi build system is very 
simple, so I don’t expect a lot of problems arising from this change. Note: You 
can *NOT* drop in the lldb-mi source into the old folder inside the LLDB source 
tree. You need to first build LLDB and then build lldb-mi against it.

2. If you encounter bugs with lldb-mi, please file a report on the GitHub 
project and *NOT* on the LLVM bugzilla. We closed all lldb-mi bugs on bugzilla, 
so if you think your issue with lldb-mi still exists, please copy your bug 
report to GitHub.

In other news: lldb-mi is also in need of a maintainer!

The good thing is that with this change lldb-mi you can now make pull requests 
against the project, we set up a CI system and in general its easier to get 
started with lldb-mi. Note that during the move lldb-mi lost its test suit, 
meaning that there are currently no tests run in the CI. This was mostly 
because we couldn’t port over the old test suit (which depended on the internal 
LLDB python test suit) and because most of the tests we had were anyway 
disabled due to random failures. If you want to get started, feel free to make 
pull requests with tests (preferable more reliable than the old ones we had).

I’m mostly writing this as the change was buried in the RFC thread last month 
and it seems all downstream folks are still completely unaware this.

TL;DR: LLDB no longer provides the lldb-mi executable. You now need to 
get lldb-mi from the GitHub repository above.

Cheers,
- Raphael

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev