[Mono] MonoAOTCompiler task does not output shared object file extension (.dylib/.so/etc.)

[naricc]

When AOTing use the MonoAOTCompiler task, the aot object files will have either a dll.o, dll-llvm.o, or a .s extension, depending on the OutputType parameter. However, on desktop these are actually shared object files and should have the appropriate extension (.dylib or .so, depending on the platform), or else the runtime will not find and run the AOT'd code.

My proposal is to add another value the ObjectType enum, maybe "Shared", to control this.

[SamMonoRT]

@steveisok @directhex - Many changes related to aot object files went in over the last month. Does any of those address this issue and do we really need this for .NET6 ?

[steveisok]

We do need this for net6. Android in particular has asked and is something @akoeplinger has been working on.

I would expect a side benefit for it to work on desktop.

[SamMonoRT]

Assigning to @akoeplinger for easy tracking

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

When AOTing use the MonoAOTCompiler task, the aot object files will have either a dll.o, dll-llvm.o, or a .s extension, depending on the OutputType parameter. However, on desktop these are actually shared object files and should have the appropriate extension (.dylib or .so, depending on the platform), or else the runtime will not find and run the AOT'd code.

My proposal is to add another value the ObjectType enum, maybe "Shared", to control this.

Author:	naricc
Assignees:	akoeplinger
Labels:	area-Codegen-AOT-mono, area-Infrastructure-mono
Milestone:	6.0.0