udacity/RoboND-Kinematics-Project

/home/srivijaykalkipoosarla/catkin_ws/src/RoboND-Kinematics-Project/gazebo_grasp_plugin/src/GazeboGraspGripper.cpp: In member function ‘bool gazebo::GazeboGraspGripper::Init(gazebo::physics::ModelPtr&, const string&, const string&, const std::vector<std::__cxx11::basic_string<char> >&, bool, std::map<std::__cxx11::basic_string<char>, boost::shared_ptr<gazebo::physics::Collision> >&)’: /home/srivijaykalkipoosarla/catkin_ws/src/RoboND-Kinematics-Project/gazebo_grasp_plugin/src/GazeboGraspGripper.cpp:53:66: error: ‘class gazebo::physics::World’ has no member named ‘GetPhysicsEngine’; did you mean ‘SetPhysicsEnabled’? physics::PhysicsEnginePtr physics = this->model->GetWorld()->GetPhysicsEngine();

sri-vijay-kalki opened this issue · 6 comments

I am very new to ROS i am getting this error while running "catkin_make" command after cloning this git file after that a big error continues regarding "GazeboGraspGripper.cpp". other thing i found is every error that comes is from cpp files in the folder please help me find a solution. I stuck here.it stopped at 89%of building.
EDIT: I changed to Eigen::Isometry3d which helps me get rid of first error.
Screenshot from 2020-06-28 19-58-24

Which version of ROs and gazebo are you using ?
Gazebo should be greater than 7.x and ideal to use in Ros Kinetic

Hope this helps.
Pavan K

Which version of ROs and gazebo are you using ?
Gazebo should be greater than 7.x and ideal to use in Ros Kinetic

Hope this helps.
Pavan K

yes, it is 9.0 version of gazebo. and i am using ROS melodic. please help me get out of it.

Expected! I had the same issue in melodic. This version of code works well with kinetic.

What should I have to do now? Any idea apart from installing ros kinetic

@poosarla-sri-vijay-kalki I recommend you to just edit the code by replacing the gazebo 7 API with Gazebo 9 API. It should be straightforward. You can search for gazebo 9 migration guide in Google, that would make your work 10times easier.

@poosarla-sri-vijay-kalki please don't close the Issue unless it is resolved implicitly, I highly recommend you to open a pull request with the Melodic changes, so it will help the upcoming people