being generated the path containing the generated code is not necessarily on the PYTHONPATH. If the test itself depends on Python code which is e.g. One example is a rostest being run as part of the tests. If you want to see the command lines used to run the compiler and linker, run catkin_make with this option: $ catkin_make -DCMAKE_VERBOSE_MAKEFILE=ONįeel free to read more details about the inner workings of catkin_make or continue on to the next tutorial: Overlaying catkin packages using workspaces.Īll commands being executed as part of CMake and make use the same environment as the invocation. If you have a previously compiled workspace and you add a new package inside it, you can tell catkin to add this new package to the already-compiled binaries by adding this parameter: $ catkin_make -force-cmake $ catkin_make install -DCMAKE_INSTALL_PREFIX=/opt/ros/groovy # might need sudo For instance, when building ROS from source you can use the 'install' target to install it to the system by passing the CMake argument ' -DCMAKE_INSTALL_PREFIX=/opt/ros/groovy' to catkin_make:

The install space is useful when you are ready to distribute or 'install' the packages in your workspace. The devel space is useful when you are developing on the packages in your workspace, because then you don't have to invoke the install target each time, which is particularly useful when developing on Python or when running tests. Note you should use either the install space or the devel space, not both at the same time. Sourcing one of these setup.*sh files will overlay this install space onto your environment. Now there should be an install space ( ~/catkin_ws/install), which contains its own setup.*sh files. This will be equivalent to calling ' cd ~/catkin_ws/build & make install'. For instance, you can tell it to make the install target: If you want you can pass any arguments you would normally pass to make to catkin_make. Also in the devel space there will be setup.*sh files generated, which when sourced will prefix your environment with this devel space. However, any generated files such as libraries, executables, or generated code will be placed in the devel space. Any source files, python libraries, scripts or any other static files will remain in the source space. This will build any packages in the source space ( ~/catkin_ws/src) to the build space ( ~/catkin_ws/build). Note: You might want to select a different CMake build type (e.g.

The Dark Knight instal the new