CMake

Yes. Again, Google can do whatever it likes with its repositories. This is entirely unrelated to whether or not the software is proprietary. Compare Google's practices here to Qt's[1], CMake's[2], or any other large open source project that is primarily maintained by a single company. To be abundantly clear: I don't think this is a good way to run an open source project, but it is a legitimate way to run one. So long as the source code and standards (insofar as they exist) are themselves permissive, then the community details are just that. [1]: https://wiki.qt.io/Qt_Contribution_Guidelines [2]: https://github.com/Kitware/CMake/blob/master/CONTRIBUTING.rs...

CMake is pretty simple internally. Every "keyword" is a function call. Every function call is implemented as a class. The simplest way to hijack it would be to have a function that calls out to your external interpreter/tool with the state you want. I could see doing that in a couple of ways: * Add a builtin command [1] that takes a string or filename and calls the interpreter with any additional data you want to pass. * Add a flow control command [1] that passes the inline block to the interpreter of your choice. You'd probably have to override cmFunctionBlocker as well for this. Note that this can't fix the deep design issues in CMake like the insane string representation. And no, I'm definitely not in therapy from CMake-induced PTSD. [1] https://github.com/Kitware/CMake/blob/master/Source/cmComman...