Opened 3 years ago
Closed 2 years ago
#62961 closed defect (fixed)
dotnet ports: arm support tracking
Reported by: | mascguy (Christopher Nielsen) | Owned by: | tsabirgaliev (Tair Sabirgaliev) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | arm | Cc: | |
Port: | dotnet |
Description
Our new dotnet-* ports don't support ARM builds yet, as Microsoft is still working on it. Nonetheless, this ticket will help track the status.
Of note, upstream's tentative plan is to only support ARM for newer .NET versions, so we won't necessarily see it across-the-board.
A good place to start, relative to Microsoft's progress:
Change History (6)
comment:1 Changed 3 years ago by mascguy (Christopher Nielsen)
comment:2 Changed 3 years ago by mascguy (Christopher Nielsen)
It looks like .NET 6.0 - the SDK, runtime, and ASP.NET core runtime - now supports ARM:
https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md#macos
These aren't quite officially released yet - as of this writing, they're at Preview 4 - but should be getting close to final.
comment:3 Changed 3 years ago by tsabirgaliev (Tair Sabirgaliev)
@macsguy the -devel port at the moment tracks .net “Current” version, whereas 6.0 branch is more suitable for -devel port. That is why initially I proposed dotnet-current as a way to track “Current” branch.
comment:4 Changed 3 years ago by tsabirgaliev (Tair Sabirgaliev)
@macsguy see https://github.com/macports/macports-ports/pull/14324
please help me test this on arm64
comment:5 Changed 3 years ago by tsabirgaliev (Tair Sabirgaliev)
comment:6 Changed 2 years ago by mascguy (Christopher Nielsen)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Given the various updates over the past few months, we're in good shape. Closing.
Microsoft is also posting updates via this Twitter post:
https://twitter.com/runfaster2000/status/1279821716944900096