Remote Development: builds successfully but find_package fails when loading cmakelists.txt
Remote development for the Nvidia Jetson with the stereolabs zed camera, the line
find_package(ZED 2 REQUIRED)
creates the error:
"By not providing "FindZED.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "ZED", but
CMake did not find one.
Could not find a package configuration file provided by "ZED" (requested
version 2) with any of the following names:
ZEDConfig.cmake
zed-config.cmake
Add the installation prefix of "ZED" to CMAKE_PREFIX_PATH or set "ZED_DIR"
to a directory containing one of the above files. If "ZED" provides a
separate development package or SDK, be sure it has been installed."
I've tried to make alterations to cmakelists.txt but to no avail (I am fairly new to cmake...) The zed package is located at /usr/local/zed/ which contains zed-config.cmake file. cmake is located at /usr/share/cmake-3.10/ and there is no findZed.cmake file in the modules folder (there are other findXXXX.cmake files there).
However the project will build and run with no problem, it's just the "intellisense" that will not work because of this error. any idea how to fix it?
请先登录再写评论。
Hello!
Have you tried adding set(CMAKE_PREFIX_PATH "/usr/local/zed/") to your CMakeLists.txt and after that calling Tools | CMake | Reset Cache and Reload Project?
Hi Anna, unfortunately that didn't solve it. I've also tried LIST(APPEND CMAKE_PREFIX_PATH "usr/local/zed").
I've provided full permissions to /zed folder and everything inside... /usr/local/zed/zed-config.cmake is right there but isn't found except when i build/run the project.
I tried creating the file ZEDConfig.cmake in /usr/local/zed/ and paste in the contents of zed-config.cmake, but the error still persists.
I solved the problem by finding your answer on a different forum question https://intellij-support.jetbrains.com/hc/en-us/community/posts/360003401999/comments/360000447419
It informed me to use "Tools>Resync with Remote Hosts" and this seems to have solved the error. Thank you!