[VitisAI EP] Add GetLibraryPath API to expose execution provider plugin library paths #25817
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 PR adds functionality to expose execution provider plugin library filesystem paths through new APIs:
Changes:
GetLibraryPath()method toEpLibrarybase classGetLibraryPath()override inEpLibraryPluginto returnlibrary_path_Environment::GetExecutionProviderLibraryPath()public API for thread-safe access to EP library pathsUse Case:
Allows downstream projects (like win-onnxruntime-genai) to intelligently resolve relative custom ops library paths by using the execution provider plugin location as a base directory.
Related Downstream Work
This PR enables functionality in the win-onnxruntime-genai repository:
The downstream PR implements intelligent custom ops library path resolution that leverages the APIs introduced in this PR.
Use Case
Allows win-onnxruntime-genai to resolve custom ops libraries relative to execution provider plugin locations, enabling better deployment flexibility where custom ops can be packaged alongside EP plugins.
API Usage: