dynamic version of the libraries in lib/amd64

[muye1202]

Hi!

I'm trying to make a pybind11 module that exposes the C++ camera sdk to python in order to send images directly into neural network pipeline, and encountered a problem when trying to compile everything using CMake: right now the amd64 version of libraries are static libraries, which, as I have experimented, do not work as expected after linking with my own dynamic library that contains the pybind11 module (more specifically the problem is undefined symbols: stereo 12 start ebb) which I believe could be due to linking .a with .so libraries, can the .so library of amd64 be made available?

I can provide more details of the problem if needed.

thanks!

[xyq1223]

Hello, our R&D colleagues have provided three dynamic library files. Please leave your email address, we will send it to you in the email attachment

[muye1202]

Hello, our R&D colleagues have provided three dynamic library files. Please leave your email address, we will send it to you in the email attachment

Hi! That's great! My email is: [email protected]

Thanks again!
Muye

[xyq1223]

My pleasure

[muye1202]

Hi!

About the dynamics library you sent me, may I ask if it is possible to change the visibility of the following function when compiling the libunitree_camera.so:

1. currently, when I'm using libunitree_camera.so in my own library compilation, it gave me "undefined symbol error: _ZZN12StereoCamera12startCaptureEbbENKUlvE_clEv", which I suppose means the visibility of the function "start_capture_ebb" is defined as internal, is it possible for this to change?

2. I did a "nm libunitree_camera.so | grep StereoCamera12 '' and found that the visibility of "_ZZN12StereoCamera12startCaptureEbb '' symbol is lowercase t, which means it cannot be used in an external library.

3. If it's needed, here I attached my CMakeList.txt file
   CMakeLists.txt

I'm using the Go1 model.

[xyq1223]

Hello,we reported this problem to our R&D colleagues. There is currently no solution, but we can upload new documents later.

[muye1202]

Hello,we reported this problem to our R&D colleagues. There is currently no solution, but we can upload new documents later.

Hi!

I see, no problem.

Thanks for following this up!