h, -help show this help message and exit This verb is used to configure a catkin workspace's configuration and layout.Ĭalling `catkin config` with no arguments will display the current config andĪffect no changes if a config already exists for the current workspace and tmp/path/to/my_catkin_ws:/opt/ros/indigo This can be done with the -extend option like so:
Cmake install pkg config install#
Suppose you wanted to extend a standard ROS system install like /opt/ros/indigo. If you realize this after the fact, you still can explicitly tell catkin build to extend some result space. With the default devel space layout, this won’t build without the catkin CMake package, since this package is used to generate setup files. This requires the `catkin ` CMake package in your source spaceĪt this point you have a workspace which doesn’t extend anything. Space, but it is set to use a `linked ` devel space layout. WARNING: Your workspace is not extending any other result Initialized new catkin workspace in `/tmp/path/to/my_catkin_ws ` Install Space: /tmp/path/to/my_catkin_ws/install Log Space: /tmp/path/to/my_catkin_ws/logsīuild Space: /tmp/path/to/my_catkin_ws/buildĭevel Space: /tmp/path/to/my_catkin_ws/devel Source Space: /tmp/path/to/my_catkin_ws/src If you start with an empty CMAKE_PREFIX_PATH, the configuration summary will show that you’re not extending any other workspace, as shown below: Note that in case the desired parent workspace is different from one already being used, using the -extend argument also necessitates cleaning your workspace with catkin clean. This is equivalent to sourcing a setup file, building, and then reverting to the environment before sourcing the setup file.įor example, regardless of your current environment variable settings (like $CMAKE_PREFIX_PATH), using -extend can build your workspace against the /opt/ros/indigo install space. With catkin config, you can explicitly set the workspace you want to extend, using the -extend argument. This is also sometimes referred to as “workspace chaining” and sometimes the extended workspace is referred to as a “parent” workspace. Normally, a catkin workspace automatically “extends” the other workspaces that have previously been sourced in your environment.Įach time you source a catkin setup file from a result-space (devel-space or install-space), it sets the $CMAKE_PREFIX_PATH in your environment, and this is used to build the next workspace. Explicitly Specifying Workspace Chaining ¶
0 kommentar(er)
