Closed ccqedq closed 7 months ago
Any specific reason why you are using v0.18.0?
I am using this version to adapt to the previous code. I see that you have implemented your own log method in the latest version of v1.4.3. If this issue is not present in the latest version, we can update the camera driver code to the latest version. Could you please confirm that?
Indeed, the dependency to glog was removed in ifm3d 1.3.2 (and above), so you should not have the same compatibility issue.
@matthiasbeyer what version of Glog you are using can you use the same version (v0.3.5) as that of ifm3d in your application.
OR
You can try to build ifm3d with your Glog version. Provide the installed path of your glog lib to -DCMAKE_PREFIX_PATH
variable while configuring the ifm3d make build. Use ";" as separator to add multiple paths to -DCMAKE_PREFIX_PATH
.
You can try, as @lola-masson suggested and port application to use the latest version of ifm3d( v1.4.3 which supports legacy devices O3D and O3X, but this release is under experimental release). In the latest release we updated the ifm3d API for grabbing data using FrameGrabber
module and deprecated Image
and opencv
module and added C++ based buffer which can be used with OpenCV and other libraries. Please follow the migration guide to update your application.
I am not sure why you pinged me?
This must've been a typo, I think @inbangsa meant to ping @ccqedq
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
I compile the v0.18.0 code to dynamic library, when I used it in my code, it can't work. finally I found out the issue caused by glog, ifm3d use the glog, and in my code I also use the glog,how can I avoid this issue?