We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not sure if it is easy or not to make support for a new architecture without a device, but I'm ready to help with testing :-) https://www.windowscentral.com/hardware/laptops/surface/project-volterra-everything-you-need-to-know
The text was updated successfully, but these errors were encountered:
For https://github.com/BashSupport-Pro, I was able to successfully build winpty for Windows ARM64:
Related: For pty4j, building win-helper.exe was also possible. But I couldn't find a Cygwin build for Windows Arm64 to build the cygwin helper.
Sorry, something went wrong.
VS 2017 Community on x64 host is also enough to cross-build ARM64 target. You'll need some additional (ARM64) components, though.
@bulenkov we're using our fork with some additional stuff JetBrains/winpty/get_current_directory for quite long time already. So I've added one more branch on top of that — JetBrains/winpty/get_current_directory_arm64, built it and used in pty4j 0.12.10
No branches or pull requests
Not sure if it is easy or not to make support for a new architecture without a device, but I'm ready to help with testing :-)
https://www.windowscentral.com/hardware/laptops/surface/project-volterra-everything-you-need-to-know
The text was updated successfully, but these errors were encountered: