You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, fantastic project. Does it run AOT compiled, something like on CoreRT run-time?
I know CoreRT is far from finished, but you get the point. May be using LLVM infrastructure to some C++ minimal run-time, similar to what .NET Native does (UWP)... ?
The text was updated successfully, but these errors were encountered:
@nawfalhasan, Thanks for asking this! This is one of the secret goals that I've been itching to add to the docs since day one, but it isn't there simply because of the fact that I never tested it :)
This is one of the key driving factors for me to invest time in this. But as you said, CoreRT is far from finished. I wanted to ensure that when CoreRT is usable, WinApi should go along right away. Infact, that's also one of the reasons I decided to split out several mundane abstractions, like Rect, Point, Size, Color, and so on, into NetCoreEx (https://github.com/prasannavl/NetCoreEx) - very early stage though. So that certain programs don't end up blocking on some huge library that doesn't compile into native for whatever reason.
That being said, is it usable today?
The simple answer is I haven't tested it. But, of the top of my head, there isn't any complex scenario that would make it difficult to work with CoreRT. I wanted to ensure that all the functional components are in place, before testing out the native compilation.
First of all, fantastic project. Does it run AOT compiled, something like on CoreRT run-time?
I know CoreRT is far from finished, but you get the point. May be using LLVM infrastructure to some C++ minimal run-time, similar to what .NET Native does (UWP)... ?
The text was updated successfully, but these errors were encountered: