Anna
Anna
You can download this package from PyPI: https://pypi.org/project/gay/
Could you [rebase](https://git-rebase.io/) commits for cleaner logs?
So `nimgendeps` is a wrapper around `nim c`? Very clever!
Also I'd: 1) pass all unknown options to Nim 2) add "--nim" option to set Nim executable 2) respect "--nimcache" option 3) add help output
Depfile should be written not for "src" but for out binary.
Should I remove `--excludeNimbleDir` option and do the following instead: add `options.config.nimbleDir` only if there are no other Nimble dirs?
Moreover, `nimble install` builds the package even when `nimble build` has been already run, so there's no way to separate compilation and installation. If it was possible, I'd be able...
It requires completely different design. Nimble is a package manager, not a build system.
Use the following pragmas: ```nim {.passCflags: staticExec("pkg-config --cflags mydep").} {.passLflags: staticExec("pkg-config --libs mydep").} ```
File collisions can be resolved downstream.