Closed iMonZ closed 3 years ago
How would we verify that? I only have a Windows Surface X, and my MBP is 2015 Intel. Without actual HW on our end this is going to be a very brittle release.
How would we verify that? I only have a Windows Surface X, and my MBP is 2015 Intel. Without actual HW on our end this is going to be a very brittle release.
Hey, I have an arm64 MacBook and arm64 Linux device :)
How would we verify that? I only have a Windows Surface X, and my MBP is 2015 Intel. Without actual HW on our end this is going to be a very brittle release.
Hey, I have an arm64 MacBook and arm64 Linux device :)
I would like to help it myself but your build system is not compatible with my system (visual studio)
How would we verify that? I only have a Windows Surface X, and my MBP is 2015 Intel. Without actual HW on our end this is going to be a very brittle release.
Hey, the macOS build SDK is 10.13 do you know where this is defined or how to change this? This is definitely too low!
I don't think we are doing anything with macOS SDKs, that must be implicit through either .NET Core or maybe Avalonia?
So we need to wait until .NET 6.0 is released
But still the current .NET SDK is using the X15 SDK and the latest artefact of ILSpy is using the X13 one which I just don't understand.
Oh, right, Scott Hunter mentioned M1 + .NET 5 RTM too close together during his .NET Conf Focus Windows talk.
This issue is going to be continued here: #56
Please add an arm64 build for linux and macOS