-
-
It would be nice if there were an optional for this! `--ninja-path` or similar.
The use case is embedding Craftr in bigger build systems (Debian, Eclipse) where you have some sort of contained filesy…
-
Files that are not executables (but scripts) should be invoked via `cmd /c`, but in this case there is a command-line length limit. See #67
-
I get this error with the current git snapshot (2.0) and can't run it.
-
The option is supported by compilers and is used in Ninja, so this warning must be wrong.
-
I thought it a good idea to have the c source in the README.md and changed the build sentence, see #139.
-
This happens with both the PyPI version and git master:
```
Could not find a version that satisfies the requirement nr.utils==1.0 (from craftr-build==1.1.2) (from versions: )
No matching distributi…
-
-
If you're declaring the same target with the same command over and over again, you will have the command duplicated every time in a new rule. We should split a `Target` into `Rule` and `Build`, just l…
-
Unfortunately, Ninja does not currently support this natively, but there are workarounds. On Posix, we can prefix the command-line string with `VAR1=value1 VAR2=value` etc. and on Windows we can write…