No rule to make target x64

[01binary]

Hello,

I am following this tutorial to build dynamixel workbench on Raspberry Pi 4 (Raspbian) and ROS Melodic:
https://emanual.robotis.com/docs/en/software/dynamixel/dynamixel_workbench/#linux-and-macos

Getting this error after running "make":

No rule to make target '/usr/local/lib/libdxl_x64_cpp.iso'

I went into /lib and all the output files I have are for the sbc platform because I am on Pi. Why is it trying to make it for x64 if I am on SBC?

libdxl_sbc_cpp.so
libdxl_sbc_cpp.so.2
libdxl_sbc_cpp.so.2.0
libdxl_sbc_cpp.so.2.0.0

Thank you!

[01binary]

Oh, got it. CMakeLists.txt in /dynamixel_workbench/dynamixel_workbench_toolbox/examples has this statement:

if (APPLE)
 target_link_libraries(....libdxl_mac_cpp.dylib")
else()
 target_link_libraries(...libdxl_linux64_cpp.so")
endif()

I changed the 64-bit instruction to sbc and now it builds on raspberri pi. That must be why it built on mac and linux VM with no issue.

[01binary]

Looks like this is the same as #294

[eisulimma]

Hey I had the same issue but your solution didn't work for me. I get the same error but with a different name:
make[2]: *** No rule to make target '/usr/local/lib/libdxl_sbc_cpp.so', needed by 'find_dynamixel'. Stop.
make[1]: *** [CMakeFiles/Makefile2:108: CMakeFiles/find_dynamixel.dir/all] Error 2
make: *** [Makefile:84: all] Error 2

Please help!
Thank you !!

[yun-goon]

Hi @01binary
Sorry for the delayed response.
The issue seems to be caused by a whitespace on line 56 of the c++/build/linux_sbc/Makefile, which resulted in the make command failing. This has been fixed in pull request #634.

Additionally, you can modify the CMakeLists.txt file to ensure it builds without issues on SBCs (like the Raspberry Pi). Add the following line at the specified location:

dynamixel-workbench/dynamixel_workbench_toolbox/examples/CMakeLists.txt

Line 19 in 31f1c97

elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "arm" OR CMAKE_SYSTEM_PROCESSOR MATCHES "aarch64")

Thank you for raising the issue!

[01binary]

@eisulimma can you verify the fix worked for you by chance so this GitHub issue can be closed cleanly?

I moved on to using NUCs which run ordinary Ubuntu desktop, and no longer using Raspberry Pi for robotics.