#machine-learning #openvino #ml #neural-network #latest-version #env-var #config-file

openvino-finder

A helper crate for finding OpenVINO installations on a system

12 unstable releases (4 breaking)

0.7.2 Jun 26, 2024
0.6.0 Dec 11, 2023
0.5.0 Apr 6, 2023
0.4.2 Oct 21, 2022
0.3.2 Jun 17, 2021

#525 in Development tools

Download history 3879/week @ 2024-03-14 3749/week @ 2024-03-21 4191/week @ 2024-03-28 4410/week @ 2024-04-04 6314/week @ 2024-04-11 6627/week @ 2024-04-18 5491/week @ 2024-04-25 7320/week @ 2024-05-02 7125/week @ 2024-05-09 13971/week @ 2024-05-16 8919/week @ 2024-05-23 11927/week @ 2024-05-30 10923/week @ 2024-06-06 15147/week @ 2024-06-13 14399/week @ 2024-06-20 13221/week @ 2024-06-27

55,830 downloads per month
Used in 8 crates (2 directly)

Apache-2.0

19KB
221 lines

openvino-finder

A utility for locating OpenVINO™ files on a host system. Consult the docs for an in-depth description of how to use this crate (and troubleshoot issues).


lib.rs:

This crate provides a mechanism for locating the OpenVINO files installed on a system.

OpenVINO can be installed several ways: from an archive, from an APT repository, via Python pip. The Rust bindings need to be able to:

  1. locate the shared libraries (e.g., libopenvino_c.so on Linux) — see find
  2. locate the plugin configuration file (i.e., plugins.xml) — see find_plugins_xml.

These files are located in different locations based on the installation method, so this crate encodes "how to find" OpenVINO files. This crate's goal is to locate only the latest version of OpenVINO; older versions may continue to be supported on a best-effort basis.

Problems with the OpenVINO bindings are most likely to be due to "finding" the right files. Both find and find_plugins_xml provide various ways of configuring the search paths, first by examining special environment variables and then by looking in known installation locations. When installing from an archive, OpenVINO provides a setup script (e.g., source /opt/intel/openvino/setupvars.sh) that sets these special environment variables. Note that you may need to have the OpenVINO environment ready both when building (cargo build) and running (e.g., cargo test) when the libraries are linked at compile-time (the default). By using the runtime-linking feature, the libraries are only searched for at run-time.

If you do run into problems, the following chart summarizes some of the known installation locations of the OpenVINO files as of version 2022.3.0:

Installation Method Path Available on Notes
Archive (.tar.gz) <extracted folder>/runtime/lib/<arch> Linux <arch>: intel64,armv7l,arm64
Archive (.tar.gz) <extracted folder>/runtime/lib/<arch>/Release MacOS <arch>: intel64,armv7l,arm64
Archive (.zip) <unzipped folder>/runtime/bin/<arch>/Release Windows <arch>: intel64,armv7l,arm64
PyPI <pip install folder>/site-packages/openvino/libs Linux, MacOS, Windows Find install folder with pip show openvino
DEB /usr/lib/x86_64-linux-gnu/openvino-<version>/ Linux (APT-based) This path is for plugins; the libraries are one directory above
RPM /usr/lib64/ Linux (YUM-based)

Dependencies

~91KB