Begin building net7.0-android TF.
#809
Merged
+16
−11
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today, we only build these packages with
net6.0-android. One consequence of how .NET Android is distributed is that no matter which .NET SDK we use (like .NET 7),net6.0-androidprojects download and are built with the .NET 6 Android SDK. This means we are using an oldgeneratorthat does not have improvements we made in the .NET 7 or .NET 8 timeframe.One particular
generatorimprovement we want in this repo is @RestrictTo support, which will help users avoid API that Google considers "internal" and thus may change without warning.We updated the .NET Android 7 targets files to allow a custom
generatorto be specified using an MSBuild property. However this only works withnet7.0-android. (We could not backport it to .NET Android 6 because it is EOL and we are no longer shipping updates for it.)In preparation for using an updated
generator, let's begin buildingnet7.0-androidnow. This will allow us to haveapi-diffagainst anet7.0-androidbaseline when we updategenerator.Unfortunately, this does increase build times temporarily until we are able to stop supporting Classic XA next year and are able to remove the
MonoAndroid12.0andnet6.0-androidframeworks.