Developping two local packages (binary and library) simultaneously

[Cornichon622]

I'd like to develop a library and a binary which uses this library, each in their directory/package, at the same time.

From Nimble's readme, I see multiple solutions:

• using nimble install every time I make a change to my library, which is not practical at all for a tight feedback loop.
• using nimble develop, but I'm unable to figure out how it works and what it does exactly. I don't even understand if I'm supposed to use it in the binary package or the library package.

I'm using Nim 2.0.0 and Nimble 0.14.2.

Have I missed something?

[penguinite]

You might be able to use a nim config file to fix this instead.

So, suppose you have the library in ~/library/ and the binary in ~/binary, you could make a nim.cfg file with --path=../library/src and insert it in the binary project.

Just remember to change the paths of course.

[Cornichon622]

Thank you for the answer. I finally made it work by using nimble develop -a as shown in #1124.

I think the documentation of the develop command isn't clear enough for beginners. A few use cases and examples would help; currently it mentions develop files and old style links which does not mean anything to a newcomer.

The fact that this subcommand is used to clone distant packages and to put local packages in development mode at the same time hasn't helped me either.