Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Building only ROS messages or services

asked 2012-10-15 06:22:13 -0500

PerkinsJames
506 ●10 ●15 ●25

Is there a way to only build ROS message or services without building the entire package? I sometimes want to separate the building of the entire package and just the messages to more concisely determine if I have an issue.

Thanks!

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2012-10-15 06:25:14 -0500

Lorenz

22731 ●129 ●202 ●316 http://ias.in.tum.de/p...

Normally, people just create a package that does not contain anything but messages to split up the dependency tree and to not force the user to compile source code if she just wants messages. You can find many examples for this in ROS, for instance nav_msgs, geometry_msgs, std_msgs, etc.

edit flag offensive delete link

Comments

+1 A separate message and service package is a best-practice that almost everyone should follow.

joq ( 2012-10-15 08:15:43 -0500 )edit

add a comment

Question Tools

1 follower

Stats

Asked: 2012-10-15 06:22:13 -0500

Seen: 1,025 times

Last updated: Oct 15 '12

Building only ROS messages or services edit

1 Answer

Comments

Question Tools

Stats

Related questions

Building only ROS messages or services