-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
Extensions do not work on full trimming (audit Activator usage) #2010
Comments
Took a quick peek. The vast majority of cases just need Cases like this, though, will never be trimming-compatible, I don't think: Silk.NET/src/Input/Silk.NET.Input.Common/InputWindowExtensions.cs Lines 99 to 122 in 3870647
Unless we can somehow abuse |
Since we build for TFMs that don't have |
Yeah the paths you linked are only used in non-AOT scenarios - users are already expected to use GlfwWindowing.Use and friends to register the platforms today on AOT. I agree with your assessment as well, it seemed like this was just a case of adding attributes. It would be nice if we didn’t need to use the Activator at all, which in theory could be possible using static abstracts in interfaces but only on newer platforms, so I guess we can deal with it for now. So in any case we’ll need to add some TFM hackery. We probably shouldn’t pull in PolySharp as we try to avoid pulling in non-.NET Foundation packages in core projects. Recommend an #ifdef or something similar to how I handled RequiresLocationAttribute. |
Modified the CoreRTTest project to add a TryGetExtension call with PublishAot=true, PublishTrimmed=true, and TrimMode=full. Fixed with the changes in #2115 |
Easy issue. May need some linking attributes littered some places. Reported in Discord.
The text was updated successfully, but these errors were encountered: