You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the analyzer reports dependencies for the platform ORT runs on. While that might be somewhat okay for a local use of ORT, it might not be okay when running ORT in a pipeline / as a service. Because such a hosted ORT usually runs on Linux, but you might want to get Windows-specific dependencies, because that's the exclusive platform you build your product for.
This basically could be implemented by teaching ORT to "fake" / pretend to be running on a configurable platform. Then either only the desired, or even all (supported) platforms could be analyzed.
Another, very expensive, work-around would be to really run ORT on all supported / desired platforms, and merge the results.
In either case, we'd need to extend our data models to also capture the platform-specificity of a dependency.
The text was updated successfully, but these errors were encountered:
Currently, the analyzer reports dependencies for the platform ORT runs on. While that might be somewhat okay for a local use of ORT, it might not be okay when running ORT in a pipeline / as a service. Because such a hosted ORT usually runs on Linux, but you might want to get Windows-specific dependencies, because that's the exclusive platform you build your product for.
This basically could be implemented by teaching ORT to "fake" / pretend to be running on a configurable platform. Then either only the desired, or even all (supported) platforms could be analyzed.
Another, very expensive, work-around would be to really run ORT on all supported / desired platforms, and merge the results.
In either case, we'd need to extend our data models to also capture the platform-specificity of a dependency.
The text was updated successfully, but these errors were encountered: