Project

General

Profile

Statistics
| Branch: | Revision:

robobuggy / buggygazebo / robobuggy_description / CMakeLists.txt @ 0e182761

History | View | Annotate | Download (5.13 KB)

1
cmake_minimum_required(VERSION 2.8.3)
2
project(robobuggy_description)
3

    
4
## Find catkin macros and libraries
5
## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz)
6
## is used, also find other catkin packages
7
find_package(catkin REQUIRED)
8

    
9
## System dependencies are found with CMake's conventions
10
# find_package(Boost REQUIRED COMPONENTS system)
11

    
12

    
13
## Uncomment this if the package has a setup.py. This macro ensures
14
## modules and global scripts declared therein get installed
15
## See http://ros.org/doc/api/catkin/html/user_guide/setup_dot_py.html
16
# catkin_python_setup()
17

    
18
################################################
19
## Declare ROS messages, services and actions ##
20
################################################
21

    
22
## To declare and build messages, services or actions from within this
23
## package, follow these steps:
24
## * Let MSG_DEP_SET be the set of packages whose message types you use in
25
##   your messages/services/actions (e.g. std_msgs, actionlib_msgs, ...).
26
## * In the file package.xml:
27
##   * add a build_depend and a run_depend tag for each package in MSG_DEP_SET
28
##   * If MSG_DEP_SET isn't empty the following dependencies might have been
29
##     pulled in transitively but can be declared for certainty nonetheless:
30
##     * add a build_depend tag for "message_generation"
31
##     * add a run_depend tag for "message_runtime"
32
## * In this file (CMakeLists.txt):
33
##   * add "message_generation" and every package in MSG_DEP_SET to
34
##     find_package(catkin REQUIRED COMPONENTS ...)
35
##   * add "message_runtime" and every package in MSG_DEP_SET to
36
##     catkin_package(CATKIN_DEPENDS ...)
37
##   * uncomment the add_*_files sections below as needed
38
##     and list every .msg/.srv/.action file to be processed
39
##   * uncomment the generate_messages entry below
40
##   * add every package in MSG_DEP_SET to generate_messages(DEPENDENCIES ...)
41

    
42
## Generate messages in the 'msg' folder
43
# add_message_files(
44
#   FILES
45
#   Message1.msg
46
#   Message2.msg
47
# )
48

    
49
## Generate services in the 'srv' folder
50
# add_service_files(
51
#   FILES
52
#   Service1.srv
53
#   Service2.srv
54
# )
55

    
56
## Generate actions in the 'action' folder
57
# add_action_files(
58
#   FILES
59
#   Action1.action
60
#   Action2.action
61
# )
62

    
63
## Generate added messages and services with any dependencies listed here
64
# generate_messages(
65
#   DEPENDENCIES
66
#   std_msgs  # Or other packages containing msgs
67
# )
68

    
69
###################################
70
## catkin specific configuration ##
71
###################################
72
## The catkin_package macro generates cmake config files for your package
73
## Declare things to be passed to dependent projects
74
## INCLUDE_DIRS: uncomment this if you package contains header files
75
## LIBRARIES: libraries you create in this project that dependent projects also need
76
## CATKIN_DEPENDS: catkin_packages dependent projects also need
77
## DEPENDS: system dependencies of this project that dependent projects also need
78
catkin_package(
79
#  INCLUDE_DIRS include
80
#  LIBRARIES robobuggy_description
81
#  CATKIN_DEPENDS other_catkin_pkg
82
#  DEPENDS system_lib
83
)
84

    
85
###########
86
## Build ##
87
###########
88

    
89
## Specify additional locations of header files
90
## Your package locations should be listed before other locations
91
# include_directories(include)
92

    
93
## Declare a cpp library
94
# add_library(robobuggy_description
95
#   src/${PROJECT_NAME}/robobuggy_description.cpp
96
# )
97

    
98
## Declare a cpp executable
99
# add_executable(robobuggy_description_node src/robobuggy_description_node.cpp)
100

    
101
## Add cmake target dependencies of the executable/library
102
## as an example, message headers may need to be generated before nodes
103
# add_dependencies(robobuggy_description_node robobuggy_description_generate_messages_cpp)
104

    
105
## Specify libraries to link a library or executable target against
106
# target_link_libraries(robobuggy_description_node
107
#   ${catkin_LIBRARIES}
108
# )
109

    
110
#############
111
## Install ##
112
#############
113

    
114
# all install targets should use catkin DESTINATION variables
115
# See http://ros.org/doc/api/catkin/html/adv_user_guide/variables.html
116

    
117
## Mark executable scripts (Python etc.) for installation
118
## in contrast to setup.py, you can choose the destination
119
# install(PROGRAMS
120
#   scripts/my_python_script
121
#   DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
122
# )
123

    
124
## Mark executables and/or libraries for installation
125
# install(TARGETS robobuggy_description robobuggy_description_node
126
#   ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
127
#   LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
128
#   RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
129
# )
130

    
131
## Mark cpp header files for installation
132
# install(DIRECTORY include/${PROJECT_NAME}/
133
#   DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION}
134
#   FILES_MATCHING PATTERN "*.h"
135
#   PATTERN ".svn" EXCLUDE
136
# )
137

    
138
## Mark other files for installation (e.g. launch and bag files, etc.)
139
# install(FILES
140
#   # myfile1
141
#   # myfile2
142
#   DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
143
# )
144

    
145
#############
146
## Testing ##
147
#############
148

    
149
## Add gtest based cpp test target and link libraries
150
# catkin_add_gtest(${PROJECT_NAME}-test test/test_robobuggy_description.cpp)
151
# if(TARGET ${PROJECT_NAME}-test)
152
#   target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME})
153
# endif()
154

    
155
## Add folders to be run by python nosetests
156
# catkin_add_nosetests(test)