> That is precisely what's happening
Excellent!
I'll carry on with Nimble, then
> and it looks like that Nimble is slowly obsoleting Nake by incorporating most
> (all?) of Nake's features
That is precisely what's happening
You should be able to use Nimble for most use cases nowadays.
Thanks, Andrea, for confirming my thinking.
To me, it makes a lot of sense to let a package manager handle builds, versions
and dependencies, and it looks like that Nimble is slowly obsoleting Nake by
incorporating most (all?) of Nake's features. At the very least it can explain
the overlap
Notice that nimble now supports tasks, which are custom command, scriptable
with nimscript. This should be extensible enough to cover your needs.
Nake is a build tool - I have never used it, since I find that build tools need
to be coupled to a package manager to be useful - there is no way to
> will compile not only your_program.nim, but also all imported modules
> recursively and build the final complete executable, so most of time you need
> just the compiler to build your project.
That is true, and also how I started out - mainly due to the fact that the Nim
tutorial does not
> my needs are simple
Consider first in Nim running just `nim c your_program` will compile not only
_your_program.nim_, but also all imported modules recursively and build the
final complete executable, so most of time you need just the compiler to build
your project.
The reason I am confused is because if nimble is able to handle builds (nimble
build) I would rather not have to deal with nake, if I can help it.
Nake is probably more fully featured, but my needs are simple.
Since I am totally new to Nim, I thought I'd ask you guys for advice.
Are you using
I am a bit confused about the difference between nake and nimble when it
applies to project management.
Coming from Rust, where I am used to use Cargo to manage my projects/builds.
I am currently using 'nimble init' to kick off a new Nim project, but I am
aware of nake, which is a build tool.
