Skip to content

Commit b24601f

Browse files
author
Changming Sun
authored
Update dependencies documentation for ONNX Runtime
1 parent 987f0a4 commit b24601f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/build/dependencies.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,9 @@ Add “--cmake_extra_defines FETCHCONTENT_TRY_FIND_PACKAGE_MODE=NEVER” to your
3838
When declaring a dependency in ONNX Runtime’s CMake files, if FIND_PACKAGE arguments are provided, FetchContent will use CMake’s FindPackage module to find dependencies from system locations. Add --cmake_extra_defines FETCHCONTENT_TRY_FIND_PACKAGE_MODE=NEVER to disable this behavior.
3939

4040
# Use preinstalled packages
41-
FetchContent is a wrapper around various CMake Dependency Providers. By default, it prefers to use FindPackage. However, there are some caveats:
41+
FetchContent is a wrapper around various CMake Dependency Providers. By default, it prefers to use FindPackage. This is the default mode when building ONNX Runtime from source. If you are integrating ONNX Runtime into a package manager(like dnf), you will need to use this approach.
42+
However, there are some caveats:
43+
4244
1. ONNX Runtime has local patches for dependencies that will not be applied to your preinstalled libraries. Most patches are not necessary for basic functionality.
4345
2. If you have installed a library version different from what ONNX Runtime expects, the build script cannot warn you. This may lead to strange build failures.
4446
3. Each library can be built in different ways. For example, ONNX Runtime expects ONNX is built with “-DONNX_DISABLE_STATIC_REGISTRATION=ON”. If you have got a prebuilt ONNX library from somewhere, most likely it was not built in this way.

0 commit comments

Comments
 (0)