-
``` python
from craftr import magic
name = magic.get_assigned_name(magic.get_frame()) + '_foo'
assert name == 'name_foo'
```
That is how it is supposed to work, but it doesn't. Instead, you get
```…
-
That would turn the current execution (and therefore override) order from
1. Environment
2. Command-Line
3. .craftrc Files
to
1. Environment
2. .craftrc Files
3. Command-line
The data from the comm…
-
On the command-line, to indicate that a target name or variable name is relative to the current main module, it should be prefixed with a dot, like `.main`.
-
Craftr generates a `default [ [...]]` declaration at the end of a ninja build file. There should be an option exclude a target from this declaration, so it will only be built if another target depend…
-
The compiler modules are currently based on `compiler.base.BaseCompiler` which implements the `objects()`, `executable()`, etc. rule functions and they use the `command()` function which must be imple…
-
Nested rule functions were supported naturally by the fact that the assigned name of the inner rule could not be determined, thus `craftr.magic.get_assigned_name()` raised a `ValueError` and the rule …
-
-
Eg. if you use `$in` in a command, it is escaped to `'$in'` by `shlex.quote()` (called by `craftr.shell.quote()`) which in turn causes multiple to `$in` not be taken as multiple arguments but only as …
-
No, but in all seriousness it should be avoided to create the build directory, then recognize there is not build manifest and then exit without deleting the build directory again.
-
If you start a subprocess and the executable can not be found, you'll see something like this
```
FileNotFoundError: [WinError 2] The system could not find the specified file
```
But no clue about w…