I did notice a bug report about a flags working in .cfg vs .nims, and I
realized that build wasn't meant to be overridden but the reason is unclear to
me. Trying to tease apart the godot-nim bindings I noticed all three ways were
used for configuration where .cfg had no logic in them.
I know you can use the @if / @else in .cfg files, but .nims seems more suited
for most things. I tried including --path in .cfg and .nims which works fine if
I run nimble and exec nim, but when I run nimble and exec nimble it's not
picked up even though the config file is read, so I had to include --path as a
flag to the exec nimble call.
For example in gonim.nimble:
task genapi, "generate bindings":
exec &"nimble c --path:deps/godot deps/genapi" # --path isn't picked up in
.cfg or .nims
I'm calling nimble in nimble because I have a dependency on the compiler
module, and the dependency check is only triggered when I exec nimble. Is there
a way to trigger the dependency check with nimble without having to call nimble
build or having to parse nimble list -i or nimble install compiler -n?
