Saves some build times, and they're not part of the usual
developer workflow.
Details
Diff Detail
- Repository
- rLLDB LLDB
Event Timeline
We need to define these variables in the cache and make sure the test suite knows about them.
For lldb-instr for example, which lives in lit/tools/lldb-instr, you'd have to configure lit.site.cfg.py.in to know about wheter it's enabled or not (for example config.have_lldb_instr) and then check for this configuration variable in the lit.site.cfg in the lldb-instr test dir.
LLDB_TOOL_$TOOL_BUILD would be a better name for consistency with llvm. In fact, if we started using the llvm cmake macros like add_llvm_subdirectory, it would handle this automatically, including creating the cache variable.
The only difference would be that the variable would default to "On", whereas you seem to want default-off. (I'm a bit torn on whether this is good. On one hand, I understand the desire to not build this stuff, but on the other, this creates an inconsistency with llvm, which builds everything by default, and consistency is a good thing.)
Also, I'd like to nominate lldb-mi as an additional optional feature. :)