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
This is now totally broken for Windows builds. It works on the Jenkins slaves because of the fallback to the cabal-install-specified location, but does not work in a distribution. This will delay the 2.1 release.
This "fix" adds two locations to the search path for Cryptol modules so that we can find the prelude on both Windows and Unix platforms. This is not ideal and should be replaced in the next version, but should have no negative impact for now unless people have multiple Cryptol.cry files hanging out in their filesystems.
If one invokes
cryptol
directly from the directory where the executable is located, it will not be able to find the Cryptol prelude.This only seems to affect binary distributions; in-place binaries in the cabal sandbox seem to have no trouble.
The text was updated successfully, but these errors were encountered: