> OK but I don't understand why you would read Ninja files rather than generate them. My build system is self-contained. It doesn't just do the configure; it c

> OK but I don't understand why you would read Ninja files rather than generate them. My build system is self-contained. It doesn't just do the configure; it can also do the build. Also, a feature is being able to treat external builds as part of the same build. For example, if one of your dependencies is a CMake project, it will be able to run the CMake configure as a target, import the targets from the Ninja file, and run those targets as part of the build for your project. It should be able to do the same for Cargo files, Zig build files, etc. That would solve the polyglot issue, minus details, which I'm working hard on. > https://news.ycombinator.com/item?id=38196412 https://news.ycombinator.com/item?id=38196412 I'm not sure why you linked the post we're commenting on... Edit: I'm also solving the Windows problem; my build system is Windows-native, and I have a design for something to build up command-lines based on the compiler in use, including MSVC. Edit 2: I also understand why you question whether anyone can solve the polyglot problem. You are right to question whether I can. If your response is "show me the code," that is rational, and my response would be, "I'm almost there; give me three months." :)