You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of #1131, nimble can build nim - however, as part of building nim-the-compiler, it also builds a toolchain including nimble - this can lead to the user instance of nimble being replaced with the version that gets compiled with nim.
when nimble installs nim as part of the dependencies of a project, it should not compile nimble and other tooling as this makes nimble shell and similar behave inconsistently as nimble gets replaced by a different version.
The text was updated successfully, but these errors were encountered:
jmgomez
added a commit
to jmgomez/nimble
that referenced
this issue
Jul 4, 2024
* draft: improves nim installation by using csources (same as atlas)
Notice when SAT is enabled, csources is stored in the cache.
Missing:
-- Proper reporting
-- Handle special versions (assume csources_2?). We could have special cases for #version-x
- Refactor to another file (nimble.nim is crazy big already)
* progress
* refactor: extract file nimenv
* Fixes an issue where the packageCache wasnt being shared in local mode
* [Green]Should be able to install different Nim versions
* fix warnings
* missing display
* fix typo
* Remove nimble from nim compilation Fixes#1175
As of #1131,
nimble
can build nim - however, as part of building nim-the-compiler, it also builds a toolchain includingnimble
- this can lead to the user instance of nimble being replaced with the version that gets compiled with nim.when
nimble
installsnim
as part of the dependencies of a project, it should not compilenimble
and other tooling as this makesnimble shell
and similar behave inconsistently asnimble
gets replaced by a different version.The text was updated successfully, but these errors were encountered: