Closed Perksey closed 4 years ago
Would love to investigate this, so assigned myself. I'm pretty sure this comes from the TryAdd to platforms, which attempts to load an assembly from a name (something like Silk.NET.Windowing.Glfw) this of course is unavailable on CoreRT
Mostly resolved with #303. I'll keep a look out to make AOT support even better, but this should suffice.
Commit 700c15cb adds a CoreRT test project to the 2.0 Silk.NET Lab.
Currently, CoreRT can't run Silk.NET projects due to the windowing system unable to resolve a platform. This could be for many reasons, as Silk.NET.Windowing uses a bit of reflection to resolve a platform as well as a custom dynamic loading system for our bindings. The current output is this:
At some point someone should investigate the cause of this issue as (in theory) everything should be working, the only part where it may be failing is the reflection.
Silk.NET.Windowing.Window
callsTryAdd
, which in turn callsAssembly.Load
and attempts to reflect through the implementation assemblies to find a platform. This could be where it's failingThat's all the insights I have to hand at the moment.