-
Notifications
You must be signed in to change notification settings - Fork 519
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
Consider default $(RuntimeIdentifier)
for MacCatalyst apps?
#15620
Comments
This seems like a good idea, adding to NET7 for consideration. |
This might also apply to |
Yes, I can confirm that this is the behaviour for IIRC @rolfbjarne wanted to ensure consistent output whatever the arch of the bots that build the app. The same logic would also apply to Catalyst apps. |
For now (maybe for .NET 7), I would consider just changing the default for |
I agree, I'll make Release builds default to be universal (for both macOS and Mac Catalyst). |
…otnet#15620. ARM64-based macOS machines are becoming more and more common, and as such it makes sense to include ARM64 builds in the app bundle when building for release. Universal builds are much slower than single-architecture builds, which is why we don't make debug builds universal. Fixes dotnet#15620.
This is fixed now. |
Steps to Reproduce
dotnet new maccatalyst
dotnet build
ordotnet build -c Release
Even on an M1, I get a
maccatalyst-x64
app.Expected Behavior
I'm thinking it should do:
Debug
- pick the RID on the machine you're building with. So an M1 gets amaccatalyst-arm64
and Intel getsmaccatalyst-x64
, and this would help the developer loop? No Rosetta when your app launches for debugging/development?Release
- defaults toRuntimeIdentifiers=maccatalyst-x64;maccatalyst-arm64
soRelease
builds get an app that supports both by default.Users can override these defaults in their
.csproj
.Actual Behavior
It seems like it just defaults to
maccatalyst-x64
? Always?Environment
I was testing with the latest .NET 6 builds.
The text was updated successfully, but these errors were encountered: