Open ognevny opened 3 weeks ago
I also encountered this error when trying to build zed v0.160.1 on windows.
I also encountered this error when trying to build zed v0.160.1 on windows.
I'm also trying to update zed for msys2!
@eternalphane this is what you can do from your side
C:\_
)C:\_\zed
for example from 1.)C:\_\python-environment-tools
)../python-environment-tools/crates/
. you need to set path for each pet* cratesource
from each pet dependency in Cargo.lock manuallyalso you can use this patch which is based on v0.159.6 tag source: https://github.com/msys2/MINGW-packages/blob/9fbd2786337c61c69b76ee63a196b3036f7f8f92/mingw-w64-zed/zed-use-vendored-pet.patch
edit: I made it possible ONLY because I have a linux machine which doesn't have this stupid restriction. it's so painful to do things on Windows...
@ognevny Or you can set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled
to 1
in registry and set core.longpaths
to true
in git
cf. rust-lang/cargo#13141
@ognevny Or you can set
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled
to1
in registry and setcore.longpaths
totrue
in git
this is not a solution in case of GitHub machine and git config probably won't work because cargo use libgit2/gix
... and git config probably won't work because cargo use libgit2/gix
Well it actually works ... just that I didn't make it compile yet 🤣
from_mode is for Unix only. a few #[cfg()] will fix it
update: looks like remote server is not supported on Windows. does cargo build -p zed
works?
by the way yes, git config thing works on GHA, but it requires to change global config, which could be bad for local builds ;(
cargo fails to checkout this repo because some files have too long path and Windows complains about it