-
Notifications
You must be signed in to change notification settings - Fork 538
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[NativeAOT] support multi-RID builds (#9826)
Context: https://github.com/dotnet/sdk/blob/68bf4cbabc023e5c2752ee4d5ce7e4a40929e748/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.RuntimeIdentifierInference.targets#L227-L229 The only blocker for supporting multi-targeted `$(RuntimeIdentifiers)=android-arm64;android-x64` builds is the error message: error NETSDK1191: A runtime identifier for the property 'PublishAot' couldn't be inferred. Specify a rid explicitly. We can set `$(AllowPublishAotWithoutRuntimeIdentifier)` by default, as this is not an error we'd ever want to show on Android. After this change I can see the MSBuild terminal logger shows the two RIDs building in parallel: NativeAOT IlcCompile (8.7s) NativeAOT IlcCompile (8.6s) And the resulting `.apk` has both `lib/arm64-v8a` and `lib/x86_64`. I also updated some of our MSBuild test infrastructure to make it easier to parameterize more MSBuild tests for `$(PublishAot)=true` in the future. We'll likely want to update tests like: [Test] public void SomeTest ([Values (true, false)] bool publishAot) { var proj = new XamarinAndroidApplicationProject (); proj.SetPublishAot (publishAot, AndroidNdkPath); // … }
- Loading branch information
1 parent
2c28801
commit b2c73ff
Showing
5 changed files
with
35 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters