Open charliermarsh opened 9 months ago
Does this mean we want support aarch64 windows? Then we need e.g. launcher binaries and some testing that puffin actually works.
I'll turn this into a more general issue. This was just about getting CI building but that makes sense. I assume I should similarly disable the i686 Windows then?
I don't understand which of the errors was the fatal one. On linux with cargo xwin build --target x86_64-pc-windows-msvc
, libgit2 compile but then the linking fails with
lld-link: error: could not open 'msvcrtd.lib': No such file or directory
@konstin This is because cargo-xwin
does not keep debug libs by default, you can pass --xwin-include-debug-libs
to keep them, or build in release mode instead.
FYI, msvcrtd.dll
is a "debug"-version of the file msvcrt.dll
.
Thank you, release mode indeed works!
Any plans here? Did it just need to be built in release mode? Windows ARM is another platform cibuildwheel supports. I also have a Windows ARM dev box that I'd like to be able to use uv on. :)
If you guys would be helped at all by someone testing or compiling on a Windows ARM machine, I have one and am happy to help!
So with the advent of the Snapdragon X chips, we're seeing Windows ARM machines become more commonplace. Older ARM chips were pretty lame, but they're dramatically improving, and dev ecosystem support is too. I have one team member who uses Windows ARM as their personal dev machine.
If someone wants to put some effort into getting an ARM build working I'm all for it. I think we could start with something low impact like the #8269 build then move to distributing releases as a secondary goal.
See: https://github.com/astral-sh/puffin/actions/runs/7673412766 (failure to build
libgit2
).See: https://github.com/astral-sh/puffin/actions/runs/7673603363 (failure to build
libgit2
, even after enabling vendoring).