How to create local packages

> What would be nice if at some future time the path could take a wildcard > parameter - e.g. `--path="./project/*"` I love this idea, thanks!

How to create local packages

OK, it seems using a higher level nim.cfg that looks down on the various packages is the best solution I can find. It does work well enough. What would be nice if at some future time the path could take a wildcard parameter - e.g. `--path="./project/*"`

How to create local packages

I use `nimble setup` for handling this. Assuming your local packages have a git repo, you might be able to do the same. `nimble setup` requires a recent nimble, so you might have to update. Add your package to your `.nimble` file with `requires`, pointing to a specific tag or commit (ex. `requi

How to create local packages

Why not fix nimble develop? It was working for alot of people until something was "fixed".

How to create local packages

Or use the "Atlas" tool which automates this setup sligthly.

How to create local packages

Use this structure: projects/projectA/module1.nim projects/projectA/module2.nim projects/projectB/module3.nim projects/projectC/module4.nim projects/nim.cfg # with the --path entries Run It "scales", what ever that is supposed to mean for a single d

How to create local packages

Yes but then one must run nimble install on every small change

How to create local packages

We had 'nimble develop' but this is kinda broken, unfortunately:

How to create local packages

you can just install your local packages with nimble. Just run `nimble install` inside your project folder, where the .nimble file is. then it will be installed into `~/.nimble/pkgs/` just like a public package

How to create local packages

Up until now, the little coding I have done with Nim has had all shared code in a single directory, and using a --path=... in the nim.cfg file for the project. This is clearly not a very scalable (nor particularly idiomatic) solution to sharing code between projects, so I am looking to put the v