Thank you. The problem was that, inside the same folder my script was i had a nim.cfg. There i have some hints off, one --import, one --path and one warnning off. I changed the location of this cfg and now everything works as expected.
By the way, my project is actually two (client and server) and my task script is defined for both. I had to make a dummy build.nim to make it work. Maybe you could change it to make task build as standalone scripts.
Just two things:
1) cpFile logs itself as mvFile: https://github.com/nim-lang/Nim/blob/master/lib/system/nimscript.nim#L164-L166
2) For some reason i get SIGSEGV: Illegal storage access. (Attempt to read from nil?) when i use mvFile. What i do now is cpFile + rmFile
I'm interested in NimScript as a portable "make-like", but I have some questions.
What's the purpose of the string in the task expression ? What's exactly the purpose of setCommand since you can control the compiler and the O.S using exec ? What is the problem encountered if we don't use setCommand "nop" ?
The string in a task describes the task. See this example: https://github.com/nim-lang/nimble/blob/master/nimble.nimble#L32
setCommand is meant to make the execution of a different command by the compiler more efficient. And setCommand "nop" is no longer needed AFAIK (definitely not needed in Nimble which also implements nimscript).