Nimble does not use the nim in the path even if it fulfills the reqs of the current proyect #1256
Comments
jmgomez
added a commit
to jmgomez/nimble
that referenced
this issue
Aug 10, 2024
## returns the nim directory prioritizing the nimBin one if it satisfais the requirement of the project ## otherwise it returns the major version of the nim installed packages that satisfies the requirement of the project (#TODO) ## if no nim package satisfies the requirement of the project it returns the nimBin parent directory ## only used by the `nimble dump` command which is used to drive the lsp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nimble does not seem to use the nim that is on the path even if it matches the deps of your current project. Because of that, if you have installed nim as a package (even if it is indirectly, e.g. if you
nimble install langserverwhich locks nim at 2.0.2), nimble prioritizes and uses that nim version (2.0.2 in that example) instead of the nim that is on the path.This is quite confusing and unexpected. What would happen if for excample you later installed some
randomlibthat locked nim 2.0.0 in its deps, usingnimble install randomlib? Would nimble suddently start using nim 2.0.0 instead of 2.0.2 when working on arraymancer which did not userandomlibin any way? Note that the only reason that arraymancer setsnim >= 1.0.0as a req in its nimble file is so that arraymancer can be used with any version of nim, so it is not feasible to change that references to something newer...The text was updated successfully, but these errors were encountered: