Fix onnxruntime static library link when linking onto C/C++ #215
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.
Issue
When building into a static library which then is linked to a C/C++ project, if you build by using
cargo build --release
the onnx runtime lib is not merged with the newly created library, and link errors arise, forcing you to link again the onnx runtime.
However, if you build by specifying the path to the libraries, such as
ORT_LIB_LOCATION=/path/to/lib cargo build --release
no issues are present.
Solution
Change the linking instructions for the default case where the downloaded onnx libraries are used, adding
static
instruction.Test
Tested on Linux x86_64, Ubuntu 22.04.4 LTS on WSL2