Create a separate Nuget hosting just managed assemblies #3104
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change has 2 parts -
Remove the coupling between the OnnxRuntime managed assembly and specific EPs. The managed ORT managed dll is now common across all EPs.
Separate out the managed OnnxRuntime assembly into a separate Nuget (Microsoft.ML.OnnxRuntime.Managed). The EP-specific native shared library artifacts will be part of separate EP-specific nugets (eg: Microsoft.ML.OnnxRuntime for CPU and Microsoft.ML.OnnxRuntime .Gpu for GPU). The "native" nuget will depend on the "managed" nuget so as to bring it into relevant projects automatically.
Resolve #2184