You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
When creating a custom driver, and trying too compile with clang++ the following error happens.
To Reproduce
Compile a driver component with clang++
CC=clang CXX=clang++ colcon build
Expected behavior
The compilation should be succes full
Logs /opt/ros/humble/include/canopen_core/node_interfaces/node_canopen_driver.hpp:198:43: error: use 'template' keyword to treat 'as' as a dependent template name auto path = this->config_["dcf_path"].as<std::string>(); /opt/ros/humble/include/canopen_core/node_interfaces/node_canopen_driver.hpp:199:37: error: use 'template' keyword to treat 'as' as a dependent template name auto dcf = this->config_["dcf"].as<std::string>();
Setup:
Device: Jetson AGX Orin 32gb
OS: ubuntu 22.04
ROS-Distro: Humble
Branch/Commit: humble
Additional context
Compiling the humble branch itself with clang/clang++ also seems to be broken, but this isn't a issue when getting it using rosdep. and only creating a custom driver.
The text was updated successfully, but these errors were encountered:
Bug description
When creating a custom driver, and trying too compile with clang++ the following error happens.
To Reproduce
Compile a driver component with clang++
CC=clang CXX=clang++ colcon build
Expected behavior
The compilation should be succes full
Logs
/opt/ros/humble/include/canopen_core/node_interfaces/node_canopen_driver.hpp:198:43: error: use 'template' keyword to treat 'as' as a dependent template name auto path = this->config_["dcf_path"].as<std::string>();
/opt/ros/humble/include/canopen_core/node_interfaces/node_canopen_driver.hpp:199:37: error: use 'template' keyword to treat 'as' as a dependent template name auto dcf = this->config_["dcf"].as<std::string>();
Setup:
Additional context
Compiling the humble branch itself with clang/clang++ also seems to be broken, but this isn't a issue when getting it using rosdep. and only creating a custom driver.
The text was updated successfully, but these errors were encountered: