This may be a controversial PR - it's meant to allow use of robowflex_dart with C++20 projects, and potentially outside of ROS/catkin contexts.
Currently, it does so by adding the ROBOWFLEX_DART_ONLY compile definition, and using this to gate the features in robowflex::darts::Robot that use parts of MoveIt that are incompatible with C++20.
This suffices to allow C++20 projects that use only the rest of robowflex_dart to build.
However, this may be incomplete (i.e., there could be other parts of robowflex_dart that also need this gating applied), and it may not be the best way to achieve C++20 compatibility.
I have also not tested this for building outside of catkin yet.
This may be a controversial PR - it's meant to allow use of
robowflex_dartwith C++20 projects, and potentially outside ofROS/catkincontexts.Currently, it does so by adding the
ROBOWFLEX_DART_ONLYcompile definition, and using this to gate the features inrobowflex::darts::Robotthat use parts of MoveIt that are incompatible with C++20. This suffices to allow C++20 projects that use only the rest ofrobowflex_dartto build.However, this may be incomplete (i.e., there could be other parts of
robowflex_dartthat also need this gating applied), and it may not be the best way to achieve C++20 compatibility. I have also not tested this for building outside ofcatkinyet.Thoughts?