JDevlieghere wrote: > Thanks for the explanation! What kind of tool reads this file?
One such tool is SWIG, which happens to support macro expansion, but we have other tools downstream that don't. > It's still weird to use tblgen to process non-td files imho. We have a bunch > of places that run python scripts as part of the build > (clang/utils/bundle_resources.py, > clang/lib/Tooling/DumpTool/generate_cxx_src_locs.py, > compiler-rt/lib/sanitizer_common/scripts/gen_dynamic_list.py, > clang-tools-extra/clangd/quality/CompletionModelCodegen.py) – maybe that > could work here? Yeah I agree and that's my fault for suggesting it in the first place to Adrian. We considered Python but weren't sure it was a hard build dependency (even though LLDB relies on it extensively, you can actually turn it off with a CMake flag). If that's the case then that's certainly a viable option. https://github.com/llvm/llvm-project/pull/89981 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
