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
I am building and running Anki on Windows using MSYS2, which generally works really well.
One significant papercut that I have run into, however, is that the pyenv directory with binaries is different on Windows (out/pyenv/scripts) as opposed to out/pyenv/bin. The bash scripts generally assume the Linux path and fail in this manner:
Since MSYS2 bash automatically appends the .exe if it is missing and an executable exists, this can be solved simply by creating a symlink from out/pyenv/bin to out/pyenv/scripts on Windows. I wanted to make a PR for this myself, but I am finding the build tooling to be a bit difficult to get a grasp on.
The text was updated successfully, but these errors were encountered:
I have gotten sufficiently frustrated with trying to build it directly on Windows and am now developing in WSL instead.
This issue can be closed, though it might be worthwhile discussing whether to explicitly recommend developing on Ubuntu in WSL for Windows users now that GUIs are supported in WSL.
I am building and running Anki on Windows using MSYS2, which generally works really well.
One significant papercut that I have run into, however, is that the
pyenv
directory with binaries is different on Windows (out/pyenv/scripts
) as opposed toout/pyenv/bin
. The bash scripts generally assume the Linux path and fail in this manner:Since MSYS2 bash automatically appends the .exe if it is missing and an executable exists, this can be solved simply by creating a symlink from
out/pyenv/bin
toout/pyenv/scripts
on Windows. I wanted to make a PR for this myself, but I am finding the build tooling to be a bit difficult to get a grasp on.The text was updated successfully, but these errors were encountered: