-
-
Notifications
You must be signed in to change notification settings - Fork 393
add support for aarch64-pc-windows-msvc #677
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
Conversation
Looks like CI fell over:
|
Rebased and updated commits now that |
Ping? |
Patch updated with the two small comments addressed. If a 0.3.7 release could be made with these changes, that would be much appreciated! |
Ping? |
1 similar comment
Ping? |
Pong? |
Comments addressed, green CI, I'm not sure what else to do here. AFAICT, the ball is in your court to either merge it or indicate what else you want done here. |
Most of the additions are where `_WIN64` was being checked, in which case we add a case next to the `target_arch = "x86_64"` checks. Other headers, particularly winnt.h, require custom AArch64-specific types.
This style is shorter, and corresponds more closer to the headers depending on _WIN64 and the like.
Blank line removed, as requested. Please review. |
Thank you! |
winapi 0.3.7 is now out. |
A lot of this is just finding places where we were conditionalizing on
target_arch = "x86_64"
and using atarget_pointer_width
test instead. The real interesting parts are inwinnt.rs
.I'm not sure of a good way to test this. Everything builds OK on
x86_64-pc-windows-msvc
, so I haven't broken anything. Unfortunately, theaarch64-pc-windows-msvc
target is in a bit of a rough state (see rust-lang/rust#53864), and I can't buildlibstd
for that target locally. I did try making theaarch64
definitions compile onx86_64
(and vice versa) inwinnt.rs
, and building with that change seemed to be OK.