Native AOT needs a manifest of input assemblies

Open
#108,036 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
compilers

Research direction

Start by examining how the ILC compiler receives input assemblies and what information is currently available when producing Native AOT binaries. Determine which assembly and package/NuGet details should be embedded, how package information could be supplied out of band, and agree on a manifest format; done means the scope and format are specified.

Written by the indexing model from the issue text.

Description

area-NativeAOT-coreclr

This is a placeholder issue for a broader question of: what info can/should we embed in Native AOT binaries?

Input assemblies are already available to the ILC compiler. Package/NuGet info is lost and would need to be provided out of band.

The format of this info is also an open question.

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.