The way targets are organized in the devel space is the same as their layout when they are installed.
The development space (or devel space) is where built targets are placed prior to being installed. The build space does not have to be contained within the workspace nor does it have to be outside of the source space, but this is recommended. CMake and catkin keep their cache information and other intermediate files here. The build space is where CMake is invoked to build the catkin packages in the source space. It can be created by calling catkin_init_workspace in the source space directory. This file is invoked by CMake during the configuration of the catkin projects in the workspace. The root of the source space contains a symbolic link to catkin's boiler-plate 'toplevel' CMakeLists.txt file. This space should remain unchanged by configuring, building, or installing. Each folder within the source space contains one or more catkin packages.
#Cmake install directory structure code#
This is where you can extract/checkout/clone source code for the packages you want to build. The source space contains the source code of catkin packages.
#Cmake install directory structure software#
Install/ - INSTALL SPACE (set by CMAKE_INSTALL_PREFIX)Ī catkin workspace can contain up to four different spaces which each serve a different role in the software development process. The following is the recommended and typical catkin workspace layout:ĬMakeLists.txt - The 'toplevel' CMake fileĬATKIN_IGNORE - Optional empty file to exclude package_n from being processedĬATKIN_IGNORE - Keeps catkin from walking this directoryĭevel/ - DEVELOPMENT SPACE (set by CATKIN_DEVEL_PREFIX)
Catkin packages can be built as a standalone project, in the same way that normal cmake projects can be built, but catkin also provides the concept of workspaces, where you can build multiple, interdependent packages together all at once.Ī catkin workspace is a folder where you modify, build, and install catkin packages.
0 kommentar(er)
