BuildFox manifest syntax is super set to ninja manifest syntax, so every ninja file is valid fox file. Sometimes it's very convenient to use BuildFox as project generator when you have ninja file. To do it you write bf -i build.ninja -o build.ninja2 --no-core --no-env --ide %your_ide%.
We should be smart and disable core, env and output at point when you write .ninja file as input file. Or maybe just add another argument like -n or something to switch to "ninja reading only mode". Then something like this is possible : bf -n --ide %your_ide%.
BuildFox manifest syntax is super set to ninja manifest syntax, so every ninja file is valid fox file. Sometimes it's very convenient to use BuildFox as project generator when you have ninja file. To do it you write
bf -i build.ninja -o build.ninja2 --no-core --no-env --ide %your_ide%
.We should be smart and disable core, env and output at point when you write .ninja file as input file. Or maybe just add another argument like
-n
or something to switch to "ninja reading only mode". Then something like this is possible :bf -n --ide %your_ide%
.