-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot find -lddsc&ddscxx #19
Comments
@Sher1ockFan I'm experiencing the same issue. Did you find a solution? |
Same issue here, the -lddsc error could be solved by The README instruction says something about setting CYCLONEDDS_HOME and CMAKE_PREFIX_PATH. Not sure what should be set to CMAKE_PREFIX_PATH though, and doesn't seems to find |
I don't know if the maintainer of the repository made a deliberate mistake or is not familiar with modern cmake.The solutions to these errors are: find_package(unitree_sdk2 REQUIRED)
include_directories(/usr/local/include/ddscxx /usr/local/include/iceoryx/v2.0.2)
# link_libraries(unitree_sdk2 ddsc ddscxx rt pthread)
link_libraries(unitree_sdk2 ddsc rt pthread) The link_target method is no longer recommended. |
Thanks so much for the solution! It worked flawlessly. |
I found the installation path was wrong |
编译unitree_mujoco时出现,cannot find -lddsc&ddscxx #19 #查找libddscxx.so locate libddscxx.so #将libddscxx.so的位置链接到/usr/local/lib/libddscxx.so sudo ln -s /home/liu/unitree_sdk2-main/thirdparty/lib/x86_64/libddscxx.so /usr/local/lib/libddscxx.so locate libddsc.so sudo ln -s /home/liu/unitree_sdk2-main/thirdparty/lib/x86_64/libddsc.so /usr/local/lib/libddsc.so |
The previous version of unitree_sdk2 was installed using install.sh. This method is no longer used in the new version. See https://github.com/unitreerobotics/unitree_sdk2. The installation paths of these two versions are inconsistent, resulting in compilation errors. |
my system is ubuntu20.04
I have installed the unitreeSDK2 on my computer
the path is /usr/local/
but there is an error about cannot find -lddsc&ddscxx occurred
The text was updated successfully, but these errors were encountered: