Revision history [back]

It's interesting that the problem is not really in octomap_server. After changing folder permissions for the local user to read and write, octomap_server and whole octomap_mapping packages are compiled normally.

But when I call rosmake 3d_navigation I get two failures regarding motion_planning_common package.

In file motion_planning_common/planning_environment/src/models I've changed the line 79:

kmodel_ = new planning_models::KinematicModel::KinematicModel(*urdf_, group_configs, multi_dof_configs);

to

kmodel_ = new planning_models::KinematicModel(*urdf_, group_configs, multi_dof_configs);

In file motion_planning_common/planning_environment/src/tools I've added

#include <boost/thread.hpp>
 
After those fixes I could successfully compile 3d_navigation package and run the simulation.
 

It's interesting that the problem is not really in octomap_server. After changing folder permissions for the local user to read and write, octomap_server and whole octomap_mapping packages are compiled normally.

But when I call rosmake 3d_navigation I get two failures regarding motion_planning_common package.

In file motion_planning_common/planning_environment/src/models I've changed the line 79:

kmodel_ = new planning_models::KinematicModel::KinematicModel(*urdf_, group_configs, multi_dof_configs);

to

kmodel_ = new planning_models::KinematicModel(*urdf_, group_configs, multi_dof_configs);

In file motion_planning_common/planning_environment/src/tools I've added

#include <boost/thread.hpp>

After those fixes I could successfully compile 3d_navigation package and run the simulation.