-
You can then write
- `ninja clean` instead of `ninja -t clean`
- `craftr clean` instead of `craftr -cc`.
-
``` python
objects = cc.compile(
sources = path.glob('src/*.c'),
include = path.local('include'), # Error! need a list, not a string
)
```
Results in an error message like this:
```
File "c:\…
-
As far as I know, you usually use `gcc`/`g++` instead of `ld` to link C object files into an executable or shared library as it does the job of invoking the linker for you. Craftr does currently not t…
-
Craftr is usually configured with the environment, just like most other build tools. The `-Dkey=value` option also just appends to the process' environment. There might be cases where you want a singl…
-
Imagine you have a rule that creates a target to create a static library from object files. This target does not only yield one file (the library), but maybe an additional file (for example a file tha…
-
The `clean` target that is automatically created is not marked explicit, thus it is run by the defaults. :-(
-
```
set MYO_SDK_PATH=..\myo-sdk-win-0.9.0
craftr -eb
```
Since Craftr switches into the build directory, the path in the environment variable is no longer valid.
-
Derived from issue #3, it should be possible to pass a linker script to linkers for Linux & OSX. Something like
``` python
from craftr.ext.compilers import get_platform_toolset as tools
ld = tools().…
-
``` 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
```…
-
It should only display output with a verbosity level >= 1.