Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RID aware .NET tools #28923

Open
Tracked by #29436
tannergooding opened this issue Nov 7, 2022 · 1 comment
Open
Tracked by #29436

RID aware .NET tools #28923

tannergooding opened this issue Nov 7, 2022 · 1 comment
Assignees
Labels
Area-Tools untriaged Request triage from a team member

Comments

@tannergooding
Copy link
Member

Today, .NET tools always target "any" and as such cannot trivially support scenarios such as https://github.com/dotnet/ClangSharp where native dependencies need to be bundled.

For https://github.com/dotnet/ClangSharp in particular, the tooling has a dependency on libClang and libClangSharp and thus needs to have some mechanism to bundle these dependencies for win-x64, win-arm64, linux-x64, and macos-x64 at a minimum.

It's worth noting support for RID specific tools would likewise allow support for AOT scenarios.

Ideally such support would also support the runtimes.json functionality so that you can have a "meta package" that then only downloads the required RID specific tool for a particular platform. This would reduce the size of NuGet packages for the common scenario.

@hansmbakker
Copy link

hansmbakker commented Dec 15, 2022

(comment removed as I understood that this issue focuses on dotnet tools rather than the wider dotnet sdk and tooling)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Tools untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

3 participants