Open pacien opened 6 years ago
Yeah, I'm afraid these aren't passed yet.
You'll have to write exec "nimble c --nimbleDir:... example/example.nim"
as a workaround in your task for now.
How can I retrieve the supplied nimbleDir
argument to pass it inside the task?
That's also not possible right now I'm afraid.
This is fixed but I want a test for it.
A custom
--nimbleDir
seems to be ignored when executing a user-defined task.Running a pre-defined task: no packages.json in the newly created nimble directory. This is expected behaviour.
Running a custom task: a packages.json is somehow found despite the custom nimble directory being empty. The dependencies are installed in the wrong directory.
dummy_nim.nimble: