-
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
[release/7.0.1xx-xcode13.3-multi-targeting] Add support for multi targeting #18884
[release/7.0.1xx-xcode13.3-multi-targeting] Add support for multi targeting #18884
Conversation
…ze the pack names. We're going to change the pack names to support multi-targetting, so ahead of the pack name change I'm changing the existing logic to use a variable for the pack name in most places (this will make the rename much easier and simpler). These changes should have no effect by themselves.
…SdkLoaded=true when loaded to ease logic in later sdks to determine the sdk to load.
…ks to contain target framework.
…sh Sdk, Ref and Runtime packs.
🔥 Failed to compare API and create generator diff 🔥 Failed to run apidiff Pipeline on Agent |
❌ [PR Build] Tests on macOS M1 - Mac Big Sur (11.5) failed ❌No test package could be found for tests on macOS M1 - Mac Big Sur (11.5) Pipeline on Agent |
🔥 [CI Build] Test results 🔥Test results❌ Tests failed on VSTS: simulator tests 0 tests crashed, 27 tests failed, 12 tests passed. Failures❌ dotnettests tests
Html Report (VSDrops) Download ❌ introspection tests
Html Report (VSDrops) Download ❌ linker tests
Html Report (VSDrops) Download ❌ monotouch tests
Html Report (VSDrops) Download ❌ msbuild tests
Html Report (VSDrops) Download Successes
Pipeline on Agent |
Test failures are unrelated (misc failures fixed in main + numerous hangs due to /~https://github.com/xamarin/maccore/issues/1124). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these docs helped clarify a lot of the initial questions I had if anyone else is reviewing and needs an additional ref! /~https://github.com/dotnet/designs/blob/main/accepted/2020/workloads/workload-manifest.md
|
Multi targetting is described here: /~https://github.com/xamarin/xamarin-macios/blob/main/docs/multi-target-framework.md
This PR implements support building using the initial .NET 7 macOS and Mac
Catalyst packages we shipped, by adding "net7.0-maccatalyst15.4" or
"net7.0-macos12.3" as a target framework.
It does so by:
Renaming the ref, sdk and runtime packs to contain the target framework and the target platfrom version, so the packages will now be named:
Microsoft.MacCatalyst.Sdk.net7.0_15.4
Microsoft.MacCatalyst.Ref.net7.0_15.4
Microsoft.MacCatalyst.Runtime.maccatalyst-x64.net7.0_15.4
Microsoft.MacCatalyst.Runtime.maccatalyst-arm64.net7.0_15.4
Microsoft.macOS.Sdk.net7.0_12.3
Microsoft.macOS.Ref.net7.0_12.3
Microsoft.macOS.Runtime.osx-x64.net7.0_12.3
Microsoft.macOS.Runtime.osx-arm64.net7.0_12.3
Only publish the above packages to NuGet (i.e. not publish the template
pack, nor the workload pack). This is because we don't need to publish any
new templates/workloads, we only need to support being included in a newer
workload.
Note that the workloads are also updated in this PR: these workloads will
never be published, but it's to keep the tests working.
Contributes towards:
net7.0-ios
+net6.0-ios
packages forces consumers to build with net7 workloads sdk#30103.This PR is best reviewed commit-by-commit.