Support for Windows ARM64 #21
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The native binaries for FreeImage are not available for Windows ARM64, so I excluded it from the benchmarks. Also, the benchmarks need to be built with portable debug symbols due to dotnet/roslyn#42393 and the
NativeMemoryProfileris unable to run on Windows ARM64 due to microsoft/perfview#1264.This was tested using my Raspberry Pi 4B (4GB ram)1 with the prebuilt libvips binaries from https://github.com/libvips/build-win64-mxe/releases/tag/v8.10.2-build2. I intend to support Windows ARM64 within the NetVips.Native NuGet package for the next release.
Benchmark results:
1: For a more realistic benchmark it would be nice to test it on a Surface Pro X as well. Does anyone have access to such device?
/cc @jcupitt, as he might be interested in the above numbers.