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
The most straightforward way of solving #8676Usability: {.experimental: “ForLoopMacros”.} is required at all macro callsites is to use --experimental:ForLoopMacros when compiling concerned projects.
To avoid having to add that everytime we can use either of:
nim.cfg
nimble tasks
nim.cfg allows all compilations to take the experimental flag into account while nimble is restricted to predefined task.
Unfortunately during Travis and Appveyor CI, the nim.cfg of the project is contaminating the compilation of koch as root folder is a clone of the project.
- cd ..- bin\nim--skipProjCfg--skipParentCfgc koch # Don't use stint's nim.cfg to compile koch-kochboot--skipProjCfg--skipParentCfg-d:release
-koch--skipProjCfg--skipParentCfg nimble
I don't have the experimental issue however a new error crops up:
main.nim(13, 10) Error: nimcore MUST be defined for Nim's core tooling
FAILURE
The command "./koch boot --skipProjCfg --skipParentCfg -d:release" failed and exited with 1 during.
The most straightforward way of solving #8676
Usability: {.experimental: “ForLoopMacros”.} is required at all macro callsites
is to use--experimental:ForLoopMacros
when compiling concerned projects.To avoid having to add that everytime we can use either of:
nim.cfg
allows all compilations to take the experimental flag into account while nimble is restricted to predefined task.Unfortunately during Travis and Appveyor CI, the
nim.cfg
of the project is contaminating the compilation ofkoch
as root folder is a clone of the project.Neither
--skipProjCfg
or--skipParentCfg
prevent this contamination: https://travis-ci.org/status-im/nim-stint/jobs/418268022#L328-L329The text was updated successfully, but these errors were encountered: