-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
urandom: compile error on Windows with Nim 2.0 #8
Comments
ee7
added a commit
to ee7/pragmagic-uuids
that referenced
this issue
Aug 6, 2023
Before this commit, compiling urandom.nim on Windows with Nim 2.0 would produce an error: $ nim c --os:windows uuids/urandom.nim /foo/pragmagic-uuids/uuids/urandom.nim(15, 8) Error: undeclared identifier: 'useWinUnicode' This was because Nim 2.0 [1] removed the useWinUnicode identifier [2]. Fix by always using CryptAcquireContextW on Windows. Fixes: pragmagic#8 [1] https://nim-lang.org/blog/2023/08/01/nim-v20-released.html [2] nim-lang/Nim@612abda
ee7
added a commit
to ee7/pragmagic-uuids
that referenced
this issue
Aug 6, 2023
Before this commit, compiling urandom.nim on Windows with Nim 2.0 would produce an error: $ nim c --os:windows uuids/urandom.nim /foo/pragmagic-uuids/uuids/urandom.nim(15, 8) Error: undeclared identifier: 'useWinUnicode' This was because Nim 2.0 [1] removed the useWinUnicode identifier [2]. Fix by always using CryptAcquireContextW on Windows. Fixes: pragmagic#8 [1] https://nim-lang.org/blog/2023/08/01/nim-v20-released.html [2] nim-lang/Nim@612abda
Fixed by #10 in v0.1.12 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Windows, Nim 2.0 produces a compile error for this package:
This is because Nim 2.0 removed
useWinUnicode
.I'll make a PR.
Maybe related: #7
The text was updated successfully, but these errors were encountered: