Post

Today I'm releasing AotAnywhere, a package which enables cross platform publishing support for dotnet NativeAOT. Before this package you had to use multiple different runners, with AotAnywhere you can publish for all targets from any single host. This is continuing the great work of @migeel.sk

Brilliant - I'm glad someone has taken the time to really polish this up! The difficulty in doing cross-OS NAOT publishing rally holds .NET back IMO.

Thanks, I needed Fable to get me over the line with this 😅 I've been trying to get this matrix green for a while now, and the final big hurdle was how to build for macOS on non-macOS hardware without shipping the SDK (which is prohibited), that's solved now by generating the stubs.

I've swapped our multi-runner job at work, and now just have a single runner producing our native cli, and it's working great.

I've got some sample projects that I want to move to this. NAOT tool packaging is a pain in the butt right now, and I think the base SDK might prevent doing multi-RID publishing for tools on the assumption that we won't ever work with it.

So I may have a suggestion for your props file that would make multi-RID NAOT tool packaging just work for folks that do use your SDK.

I think this is gonna need an SDK-level change to provide a target hook, so I've got an agent working on that now :) Will poke when I've got something for ya to look at.

Here's where I've landed: github.com/dotnet/sdk/p... The idea would be to give you a place where you can express an opinion on the set of publishable RIDs for the current 'outer' build invocation.