- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm following the instructions at https://docs.openvino.ai/2025/get-started/install-openvino.html?PACKAGE=OPENVINO_BASE&VERSION=v_2025_0_0&OP_SYSTEM=WINDOWS&DISTRIBUTION=VCPKG and I've installed the 2025 package via vcpkg.
Next I've built a simple application in C++ to list the available devices with MSVC (2022) using vcpkg to link with openvino. Basically, this is what I'm trying to do
ov::Core core; std::vector available_devices = core.get_available_devices();
for (const auto& device : available_devices) {
std::cout << "Available device: " << device << "\n";
}
No devices however seem available.
When I install openvino in a virtual environment via pip on the same machine, I can run the benchmarking application just fine. So my hardware should suffice. Somehow the vcpkg installed version isn't configured properly to find any devices?
Is there anything I've missed in the documentation when using vcpkg to ensure devices are found?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think I figured it out; not all runtime dll's are not copied to the output folder. This seems to be an issue with package itself?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think I figured it out; not all runtime dll's are not copied to the output folder. This seems to be an issue with package itself?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi hwh,
Have you done the following steps after installing OpenVINO package via vcpkg?
After installation (vcpkg install openvino), you can use OpenVINO in your product’s cmake scripts:
find_package(OpenVINO REQUIRED)
Next, run from terminal:
cmake -B <build dir> -S <source dir> -DCMAKE_TOOLCHAIN_FILE=<VCPKG_ROOT>/scripts/buildsystems/vcpkg.cmake
Regards,
Peh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, because I was not planning on using CMake. Also there should be no need for CMake, since vcpkg has MSVC integration. Usually the (necessary) runtime dll's are nicely copied to the output folder. But I might look into using vcpkg + cmake, and check out if that works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi hwh,
Any updates from your end? Looking forward to hearing how it goes!
Regards,
Peh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When trying to setup a CMake project with vcpkg support (as per Microsoft instructions here: https://learn.microsoft.com/en-us/vcpkg/get_started/get-started-vs?pivots=shell-powershell ) I run into the problem that it somehow won't find the package itself:
PS D:\Projects\test-cmake> cmake -B build -S . -DCMAKE_TOOLCHAIN_FILE=c:/vcpkg/scripts/buildsystems/vcpkg.cmake -- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.19045. CMake Error at CMakeLists.txt:14 (find_package): By not providing "FindOpenVINO.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "OpenVINO", but CMake did not find one. Could not find a package configuration file provided by "OpenVINO" with any of the following names: OpenVINOConfig.cmake openvino-config.cmake Add the installation prefix of "OpenVINO" to CMAKE_PREFIX_PATH or set "OpenVINO_DIR" to a directory containing one of the above files. If "OpenVINO" provides a separate development package or SDK, be sure it has been installed. -- Configuring incomplete, errors occurred! ...
For now I'm happy with my own solution by explicitly copying the runtime dll's to the target /outp folder.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi hwh,
Thanks for the updates.
Since you are good with your own solution, hence this thread will no longer be monitored. If you need any additional information from Intel, please submit a new question.
Regards,
Peh

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page