Open robotrapta opened 3 years ago
Thanks for reporting an issue. Because we're a volunteer community, providing a pull request with suggested changes is always welcomed.
Looks like 186f9c464351c2105daece39bbddce586f381308 might have caused this? Rolling back to edb533c14e38b4f4ec34345263a390dc59bb3a6c makes the error go away.
@henningkayser
Yes, #549 caused this, which goes in sync with https://github.com/ros-planning/moveit/pull/2127, https://github.com/ros-planning/moveit_msgs/pull/95, and https://github.com/ros-planning/moveit_resources/pull/47. Until the next release is out, you will need to build all those packages from source to use the latest versions. Alternatively, rollback moveit_tutorials as suggested in https://github.com/ros-planning/moveit_tutorials/issues/613#issuecomment-801304192.
@robotrapta sorry for the inconvenience
No worries! I understand that multi-package upgrades are tricky, but necessary for long-term code health.
I have what I need. Maybe leave this open until the release is done so it's easier for others to find the workaround? Do search engines prioritize open issues vs closed? IDK.
if you look up the source code of the MoveItCpp class, you will find the MoveItCpp's namespace is moveit::planning_interface not moveit_cpp, so replace the moveit_cpp with moveit::planning_interface, then it works.
@rhaschke Leaving a comment to share that it ain't great that the solution for fixing tutorial code is to wait for it to sync up with other released packages that as of over a month later, still don't seem to be finished. (I'm using noetic)
If the namespaces are aliased, I'm throwing in a +1 for reopening and merging https://github.com/ros-planning/moveit_tutorials/pull/614 so that future travelers aren't tripped up by this. Then, when things are synced, just change the namespacing back.
Otherwise, at minimum, leave a temporary note in the example code...? This bug is dumb.
Description
I'm getting a compiler error when following the getting started instructions for the tutorial on a clean Ubuntu 20.04+Noetic machine. (Arm64 FWIW)
Overview of your issue here.
Your environment
Steps to reproduce
On a fresh EC2 graviton instance with Ubuntu 20.04, install Noetic, and follow the tutorial setup instructions https://ros-planning.github.io/moveit_tutorials/doc/getting_started/getting_started.html
When I get to
catkin build
it crashes. Same results regardless of whether I include MoveIt source or not.Expected behaviour
Successful build
Backtrace or Console output