API version mismatch 2.30.0
I am trying to use Intel RealSense in my own project in Windows 10 and Visual Studio 2017. I have downloaded the latest version 2.30.0 from github (Windows exe installer).
When I try to initialize real sense module, I get the following error:
"RealSense error calling rs2_create_context(api_version:23000):
API version mismatch: librealsense.so was compiled with API version 2.25.0 but the application was compiled with 2.30.0! Make sure correct version of the library is installed (make install)"
In my windows applications I do not see any "2.25.0" version. How could this be? How to resolve this issue?
I have also tried to uninstall Intel RealSense SDK and install again multiple times.
-
It sounds as though you are using RealSense SDK version 2.30.0, but something in the Visual Studio project that you have created is using components that are referencing the earlier 2.25.0 SDK version and it is causing a mismatch.
One situation where this may occur is when using the RealSense ROS wrapper. Each version of the wrapper has to be used with a specific version of the RealSense SDK. For example, the previous version of the ROS wrapper required SDK 2.25.0, so would cause a mismatch if used with an SDK version that was not 2.25.0.
In the newest ROS wrapper version at the time of writing this, SDK 2.29.0 has to be used with it.
If you are not using ROS, another situation where a mismatch could occur is if you were using SDK version 2.30.0 but in your Visual Studio project you were linking to a file that was built using the earlier SDK 2.25.0.
-
Thank you for contacting Intel RealSense Customer Support,
As you updated RealSense SDK to version 2.30.0, you will need to rebuild the whole solution from the librealsense2.sln file in Visual Studio. Search for the file in <librealsense source directory/build/librealsense2.sln>, double click to open it in Visual Studio, and right click the top level solution (librealsense2) and select "build solution".
Regards,
The Intel RealSense Customer Support Team.
Please sign in to leave a comment.
Comments
2 comments