OpenTK Deprecation #5755
OpenTK Deprecation #5755
Conversation
src/Xamarin.Android.Build.Tasks/Xamarin.Android.Build.Tasks.targets
Outdated
Show resolved
Hide resolved
src/Xamarin.Android.Build.Tasks/Linker/Mobile.Tuner/MobileProfile.cs
Outdated
Show resolved
Hide resolved
dellis1972
force-pushed
the
opentkstuff
branch
2 times, most recently
from
daed95f to
b962dc9
Compare
dellis1972
force-pushed
the
opentkstuff
branch
3 times, most recently
from
78b85ac to
1381cf1
Compare
dellis1972
requested review from
jonathanpeppers and
radekdoulik
as code owners
dellis1972
force-pushed
the
opentkstuff
branch
3 times, most recently
from
7c91e6f to
c98e9c7
Compare
We are going to stop shipping OpenTK-1.0 in a future update. In order to give users who are using that assembly a chance to migrate we will deprecate it first. We will raise a `XA4313` warning if we detect that OpenTK-1.0 is in the `@(Refereces)` item group. A replacement Nuget Package has already been created at https://www.nuget.org/packages/Xamarin.Legacy.OpenTK/ Users seeing this warning should remove the reference to `OpenTK-1.0` and replace it will the following ``` <PackageReference Include="Xamarin.Legacy.OpenTK" Version="0.0.1-alpha" /> ``` The version number will change in the future. The vast majority of changes in this commit are to stop the OpenTK java types being included in `mono-android.jar`. From this point on `OpenTK` will be treated like all other Android Class Libraries, the generated java code will be written to the `$(IntermediateOutputPath)\lp` directory along with all the other references.
...n.Android.Build.Tasks/Microsoft.Android.Sdk/targets/Microsoft.Android.Sdk.BuildOrder.targets
Outdated
Show resolved
Hide resolved
|
|
||
| from your csproj then add | ||
|
|
||
| '<PackageReference Include="Xamarin.Legacy.OpenTK" Version="1.0.0" />' |
There was a problem hiding this comment.
the version should probably be 0.0.1-alpha ?
There was a problem hiding this comment.
I'll probably push a release 1.0.0 before we ship this.
I'm not sure why those are there. I suspect they will still be needed even with the Nuget. |
They need to be present somewhere, even with the NuGet, and even under .NET 6. That doesn't mean that the xamarin-android repo is the appropriate place fo the ProGuard config info. If possible, can the OpenTK-related statements within |
We are going to stop shipping OpenTK-1.0 in a future update. In order to give users who are using
that assembly a chance to migrate we will deprecate it first.
We will raise a
XA4313warning if we detect that OpenTK-1.0 is in the@(Refereces)item group.A replacement Nuget Package has already been created at https://www.nuget.org/packages/Xamarin.Legacy.OpenTK/
Users seeing this warning should remove the reference to
OpenTK-1.0and replace it will the followingThe version number will change in the future.
The vast majority of changes in this commit are to stop the OpenTK java types being included in
mono-android.jar.From this point on
OpenTKwill be treated like all other Android Class Libraries, the generated java code will bewritten to the
$(IntermediateOutputPath)\lpdirectory along with all the other references.