mizvekov wrote: > Can you elaborate on what specifically you find hard? Building should be > fairly straightforward, besides Python and SWIG, which are required to run > the tests, most of our dependencies are optional. Unlike the compiler, the > debugger is (1) tied to the system it's running on, and (2) an interactive > tool, so maybe that's what you're referring to? Either way, if there are > concrete ways we can make LLDB easier to work on, I'd love to hear your > suggestions!
This was about a year ago, and I remember @erichkeane had similar issues, but the main points: 1) Windows support 2) Build system does not support Multi-config generators. You can grep for https://cmake.org/cmake/help/latest/variable/CMAKE_CFG_INTDIR.html as an example. 3) Not all tests pass and it's quite unclear when that is not your fault. AFAIK, on windows I would run into this issue where running the LLDB test suite would cause hundreds of frozen terminal windows to spawn, and that was quite difficult to recover from without rebooting. This might be related to 2) above, before I figured it out. I eventually thought that was too dangerous to run on windows and managed to get it working on linux virtual machine. https://github.com/llvm/llvm-project/pull/94208 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
