[MONO] Add AOT compiler to desktop runtime pack

[naricc]

The runtime pack should include the mono-sgen binary for use as an AOT compiler; this simplifies a lot of testing and benchmarking tasks. It might also be useful for developers who want to test any AOT stuff with out using an iOS/Android simulator.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[radical]

/cc @lewing

[lewing]

I think the plan is to move to using the AOT compiler nugets to pull in the compiler, and remove the included one?

[lewing]

cc @steveisok

[steveisok]

@naricc I responded to you earlier w/o thinking and skipped a few important details. The pattern for our AOT compilers moving forward is to not be bundled inside the runtime pack, but within their own nuget package. At the end of the day, it'll be similar and I don't think generating an osx mono-aot-cross binary is going to be that big of a thing.

You would add something like <BuildMonoAOTCrossCompiler Condition="'$(TargetsOSX)' == 'true'">true</BuildMonoAOTCrossCompiler> below

runtime/src/mono/mono.proj

Line 39 in e4a981c

<BuildMonoAOTCrossCompiler Condition="'$(TargetsAndroid)' == 'true'">true</BuildMonoAOTCrossCompiler>

. That may get you most of the way. Then, I think it's about modifying the installer from there. @directhex would be the best person to ping.

[naricc]

So, mono-sgen is already the non-cross AOT compiler, and we already build it right? Should I close out this issue then?

[steveisok]

We build it, but do not bundle it. If we want to use it outside of runtime, then we should package it like the mobile ones.

[naricc]

Package it like the mobiles ones means put mono-sgen in its own nuget then?

[steveisok]

Presumably. I'd like to think it's as simple as that.

/cc @akoeplinger

[SamMonoRT]

@naricc @akoeplinger - is this going to be possible by Preview 7 cutoff ?

[naricc]

I don't think it is hard to do, but I have never actually done this kind of work before, so it's hard for me to give an accurate estimate. If we want to prioritize it, I don't see why it wouldn't be possible though.

[SamMonoRT]

This is a nice to have feature. Moving to 7.0, not required for 6.0.0

[naricc]

This is a useful feature, but not something we have been able to prioritize.

[kotlarmilos]

@akoeplinger Is this a requirement for .NET 8, or can it be postponed after RC1/RC2?