ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2021-09-14 10:48:28 -0500 | received badge | ● Good Question (source) |
2017-03-09 02:38:11 -0500 | received badge | ● Nice Question (source) |
2017-01-13 07:39:03 -0500 | received badge | ● Notable Question (source) |
2015-08-28 14:19:51 -0500 | received badge | ● Good Question (source) |
2015-08-27 07:16:15 -0500 | received badge | ● Great Answer (source) |
2015-08-27 07:16:15 -0500 | received badge | ● Guru (source) |
2015-06-03 10:05:21 -0500 | received badge | ● Nice Question (source) |
2014-02-20 07:33:41 -0500 | received badge | ● Taxonomist |
2014-01-28 17:28:10 -0500 | marked best answer | make without rebuilding everything everytime In my package I defined a library which is linked to my executable.. the cmakelists file looks like this: ... rosbuild_add_library(mylib src/lib_src.cpp) #in the real cmake I have lot of sources in the library rosbuild_add_executable(myexe src/exe_src.cpp) target_link_libraries(myexe mylib) ... When I run make everything is compiled. But if I run make again, everything is compiled again, even if nothing was modified. Is it possible to compile only the changed parts? In my case would be fine to recompile the changed executable without recompiling the unchanged (and huge) library. Thanks |
2014-01-28 17:27:45 -0500 | marked best answer | Documenting parameters and nodes Is there any standard way to generate documentation for nodes and parameters in a ros wiki like form? I tried with rosdoc but I'm getting only the doxygen documentation. |
2013-11-14 12:12:21 -0500 | received badge | ● Famous Question (source) |
2013-10-15 08:14:57 -0500 | received badge | ● Famous Question (source) |
2013-08-12 09:47:35 -0500 | received badge | ● Popular Question (source) |
2013-05-23 04:22:36 -0500 | received badge | ● Notable Question (source) |
2013-04-05 01:14:04 -0500 | received badge | ● Popular Question (source) |
2013-03-03 02:58:02 -0500 | received badge | ● Famous Question (source) |
2012-11-22 22:08:16 -0500 | received badge | ● Enlightened (source) |
2012-11-22 20:36:40 -0500 | received badge | ● Good Answer (source) |
2012-11-22 20:35:44 -0500 | received badge | ● Nice Answer (source) |
2012-11-22 09:55:53 -0500 | received badge | ● Notable Question (source) |
2012-11-22 05:26:42 -0500 | marked best answer | gtesting a custom class I created the test/myTest.cpp file, which includes the myClass.h header file. When I compile with make test I get the error ‘MyClass’ does not name a type, where MyClass is the class defined in myClass.h (the error is located where I declare a new MyClass variable) I think I am missing something with the cmakelists file.. What should I do to compile everything correctly? I am using ros electric.. |
2012-11-22 05:26:42 -0500 | received badge | ● Supporter (source) |
2012-11-22 04:39:36 -0500 | received badge | ● Teacher (source) |
2012-11-22 04:39:36 -0500 | received badge | ● Self-Learner (source) |
2012-11-22 04:31:38 -0500 | answered a question | make without rebuilding everything everytime Finally, after hours I have an answer.. The problem is in the cfg files. You must be sure that the filename matches the third parameter of the last line of the file, the one with the exit statement. For example if the last line is: exit(gen.generate(PACKAGE, "dummy", "myNameIsImportant")) the file name must be myNameIsImportant.cfg I did not find this information in the documentation/tutorials... |
2012-11-22 03:44:52 -0500 | received badge | ● Popular Question (source) |
2012-11-22 03:33:13 -0500 | commented answer | make without rebuilding everything everytime That dido not fixed the issue.. I also removed everything apart from a single executable but it keeps compiling.. maybe is an issue with the dyn rec gen msg... |
2012-11-22 02:37:08 -0500 | commented question | make without rebuilding everything everytime heres my cmakelists: https://gist.github.com/4131480 timestamps are ok.. |
2012-11-21 23:39:13 -0500 | commented question | make without rebuilding everything everytime Happy to hear that I am not expecting strange things :D which kind of information should I provide to help the debug? |