ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2012-10-08 18:58:38 -0500 | received badge | ● Famous Question (source) |
2012-10-08 18:58:38 -0500 | received badge | ● Notable Question (source) |
2012-08-19 06:03:40 -0500 | received badge | ● Taxonomist |
2012-05-22 09:41:38 -0500 | received badge | ● Popular Question (source) |
2012-01-04 18:35:30 -0500 | marked best answer | Error while running nodelet: cannot load library, undefined symbol You need to link the library against the library containing GridProcess symbols. If it's in another package you should add the library to the exports in the other packages manifest.xml and make sure that you depend on that package. If it's in the same package you need to use the "target_link_libraries" cmake command in you CmakeLists.txt. |
2011-12-15 07:55:41 -0500 | received badge | ● Editor (source) |
2011-12-14 20:39:09 -0500 | received badge | ● Supporter (source) |
2011-12-14 20:39:06 -0500 | commented answer | Error while running nodelet: cannot load library, undefined symbol Thanks for your answer, Although I was including gridmapping libraries but it had the same library name as gridmapping_nodelet and that was causing the issue above. Thanks for pointing me to the right direction
|
2011-12-09 05:39:45 -0500 | asked a question | Error while running nodelet: cannot load library, undefined symbol I am trying to create a nodelet out of an existing node with the header file gridmapping_nodelet.h given as and gridmapping_nodelet.cpp file is as follows nodelet_plugins.xml is given by CMakeLists.txt manifest.xml launch file The parameters are defined in a separate launch file which calls on the launch file mentioned above. The ouput error is as follows Any help is greatly appreciated Alright the library issue is resolved, thanks to Tully! But now I am facing md5sum errors, I have checked all my packages for consistency in terms in messages(by rebuilding them after clean) and the node I am converting to nodelet runs just fine. Since I don't change message types during conversion, I was surprised to see this error in the log file after my nodelet crashed - (more) |