Mirror of forum.nim-lang.org

12586 :: nimble develop with a package not in an official list

• darkestpigeon (orginal) [2024-11-06T13:08:34+01:00] view original

  I have a package A that depends on a package B. Both packages are in my private repositories. I'd like to use the nimble develop B when developing A. The package A nimble file has requires "url-to-package-B" in it. Running nimble develop B as the package B is not found is the official package list. Running nimble develop url-to-package-B clones the package, but does not update nimble.paths properly (it still points to package B in .nimble directory).

  Any way to go around this problem without manually tweaking the nimble.paths file? Or perhaps there is a better workflow for this?

---

• cmc (orginal) [2025-06-10T15:06:09+02:00] view original

  Just had something similar- you have to navigate to the package you are developing and run nimble develop, not nimble develop mypackagename. If you do that for both, you should be able to import modules from both packages in both packages. You should also run nimble develop -g in each package directory to support compiling with nim c myfile.nim rather than nimble build. Add the line nimblepath="$home/.nimble/links/" to ~/.config/nim/nim.cfg or %APPDATA%/nim/nim.cfg to enable this for all packages of your user.

---