From aba24e78540b9f4ccd34da3b294599c8ce8902f8 Mon Sep 17 00:00:00 2001 From: Brian Gerkey Date: Wed, 12 Jan 2011 23:10:52 +0000 Subject: [PATCH] removed all .msg source, because we don't need it, and it causes problem with rosbuild (#3232) --- core/roslib/msg/Clock.msg | 4 ---- core/roslib/msg/Header.msg | 15 --------------- core/roslib/msg/Log.msg | 19 ------------------- 3 files changed, 38 deletions(-) delete mode 100644 core/roslib/msg/Clock.msg delete mode 100644 core/roslib/msg/Header.msg delete mode 100644 core/roslib/msg/Log.msg diff --git a/core/roslib/msg/Clock.msg b/core/roslib/msg/Clock.msg deleted file mode 100644 index 423872fe..00000000 --- a/core/roslib/msg/Clock.msg +++ /dev/null @@ -1,4 +0,0 @@ -# roslib/Clock is used for publishing simulated time in ROS. -# This message simply communicates the current time. -# For more information, see http://www.ros.org/wiki/Clock -time clock diff --git a/core/roslib/msg/Header.msg b/core/roslib/msg/Header.msg deleted file mode 100644 index b2f34f6f..00000000 --- a/core/roslib/msg/Header.msg +++ /dev/null @@ -1,15 +0,0 @@ -# Standard metadata for higher-level stamped data types. -# This is generally used to communicate timestamped data -# in a particular coordinate frame. -# -# sequence ID: consecutively increasing ID -uint32 seq -#Two-integer timestamp that is expressed as: -# * stamp.secs: seconds (stamp_secs) since epoch -# * stamp.nsecs: nanoseconds since stamp_secs -# time-handling sugar is provided by the client library -time stamp -#Frame this data is associated with -# 0: no frame -# 1: global frame -string frame_id diff --git a/core/roslib/msg/Log.msg b/core/roslib/msg/Log.msg deleted file mode 100644 index 9a9597c2..00000000 --- a/core/roslib/msg/Log.msg +++ /dev/null @@ -1,19 +0,0 @@ -## -## Severity level constants -## -byte DEBUG=1 #debug level -byte INFO=2 #general level -byte WARN=4 #warning level -byte ERROR=8 #error level -byte FATAL=16 #fatal/critical level -## -## Fields -## -Header header -byte level -string name # name of the node -string msg # message -string file # file the message came from -string function # function the message came from -uint32 line # line the message came from -string[] topics # topic names that the node publishes