Built ONNX Runtime... now what? #22902
-
I have built ONNX Runtime from source. How do I "generate" the distributable form of it? I.e., when I download ONNX Runtime from the releases page, I get a zip containing lib/ and include/ Directly inside include/ are some header files. Directly inside lib/ are some .so files. However, include/ in the git repository of ONNX Runtime does not match the other include/ directory at all (the directory structure is much more complex than just a folder containing header files), and so the dependency that requires ONNX Runtime fails to include the header file. Additionally, there are .so files under build/Linux/Release/ in my build, but I don't know which are relevant to the redistributable zip. How do I generate the distributable form of ONNX Runtime? I don't see this mentioned in any documentation and it's difficult to figure out from the build scripts/Dockerfiles. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Why do you need to do this vs. using one of the release packages? https://github.com/microsoft/onnxruntime/releases/ or platform specific package repositories like nuget, maven, cocoapods etc. |
Beta Was this translation helpful? Give feedback.
-
All the packaging is done via CIs. You can probably refer to this: https://github.com/microsoft/onnxruntime/blob/main/tools/ci_build/github/azure-pipelines/templates/c-api-artifacts-package-and-publish-steps-windows.yml |
Beta Was this translation helpful? Give feedback.
All the packaging is done via CIs. You can probably refer to this: https://github.com/microsoft/onnxruntime/blob/main/tools/ci_build/github/azure-pipelines/templates/c-api-artifacts-package-and-publish-steps-windows.yml