catkinize

This commit is contained in:
Michael Ferguson 2013-02-02 12:43:37 -08:00
parent 3597468376
commit 12a7ca4dbb
26 changed files with 125 additions and 242 deletions

View File

@ -1,17 +0,0 @@
cmake_minimum_required(VERSION 2.4.6)
include($ENV{ROS_ROOT}/core/rosbuild/rosbuild.cmake)
# Append to CPACK_SOURCE_IGNORE_FILES a semicolon-separated list of
# directories (or patterns, but directories should suffice) that should
# be excluded from the distro. This is not the place to put things that
# should be ignored everywhere, like "build" directories; that happens in
# rosbuild/rosbuild.cmake. Here should be listed packages that aren't
# ready for inclusion in a distro.
#
# This list is combined with the list in rosbuild/rosbuild.cmake. Note
# that CMake 2.6 may be required to ensure that the two lists are combined
# properly. CMake 2.4 seems to have unpredictable scoping rules for such
# variables.
#list(APPEND CPACK_SOURCE_IGNORE_FILES /core/experimental)
rosbuild_make_distribution(0.1.0)

View File

@ -1 +0,0 @@
include $(shell rospack find mk)/cmake_stack.mk

View File

@ -0,0 +1,21 @@
<package>
<name>ros_arduino_bridge</name>
<version>0.2.0</version>
<description>
Metapackage for ros_arduino_bridge.
</description>
<author>Patrick Goebel</author>
<maintainer email="patrick@pirobot.org">Patrick Goebel</maintainer>
<license>BSD</license>
<url>http://ros.org/wiki/ros_arduino_bridge</url>
<buildtool_depend>catkin</buildtool_depend>
<run_depend>ros_arduino_firmware</run_depend>
<run_depend>ros_arduino_msgs</run_depend>
<run_depend>ros_arduino_python</run_depend>
<export>
<metapackage/>
</export>
</package>

View File

@ -1,30 +1,9 @@
cmake_minimum_required(VERSION 2.4.6) cmake_minimum_required(VERSION 2.8.3)
include($ENV{ROS_ROOT}/core/rosbuild/rosbuild.cmake) project(ros_arduino_firmware)
# Set the build type. Options are: find_package(catkin REQUIRED)
# Coverage : w/ debug symbols, w/o optimization, w/ code-coverage catkin_package(DEPENDS)
# Debug : w/ debug symbols, w/o optimization
# Release : w/o debug symbols, w/ optimization
# RelWithDebInfo : w/ debug symbols, w/ optimization
# MinSizeRel : w/o debug symbols, w/ optimization, stripped binaries
#set(ROS_BUILD_TYPE RelWithDebInfo)
rosbuild_init() install(DIRECTORY src
DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
#set the default path for built executables to the "bin" directory )
set(EXECUTABLE_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/bin)
#set the default path for built libraries to the "lib" directory
set(LIBRARY_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/lib)
#uncomment if you have defined messages
#rosbuild_genmsg()
#uncomment if you have defined services
#rosbuild_gensrv()
#common commands for building c++ executables and libraries
#rosbuild_add_library(${PROJECT_NAME} src/example.cpp)
#target_link_libraries(${PROJECT_NAME} another_library)
#rosbuild_add_boost_directories()
#rosbuild_link_boost(${PROJECT_NAME} thread)
#rosbuild_add_executable(example examples/example.cpp)
#target_link_libraries(example ${PROJECT_NAME})

View File

@ -1 +0,0 @@
include $(shell rospack find mk)/cmake.mk

View File

@ -1,26 +0,0 @@
/**
\mainpage
\htmlinclude manifest.html
\b ros_arduino_firmware is ...
<!--
Provide an overview of your package.
-->
\section codeapi Code API
<!--
Provide links to specific auto-generated API documentation within your
package that is of particular interest to a reader. Doxygen will
document pretty much every part of your code, so do your best here to
point the reader to the actual API.
If your codebase is fairly large or has different sets of APIs, you
should use the doxygen 'group' tag to keep these APIs together. For
example, the roscpp documentation has 'libros' group.
-->
*/

View File

@ -1,14 +0,0 @@
<package>
<description brief="ros_arduino_firmware">
ROS Arduino Firmware
</description>
<author>Patrick Goebel</author>
<license>BSD</license>
<review status="unreviewed" notes=""/>
<url>http://ros.org/wiki/ros_arduino_firmware</url>
</package>

View File

@ -0,0 +1,13 @@
<package>
<name>ros_arduino_firmware</name>
<version>0.2.0</version>
<description>
ROS Arduino Firmware.
</description>
<author>Patrick Goebel</author>
<maintainer email="patrick@pirobot.org">Patrick Goebel</maintainer>
<license>BSD</license>
<url>http://ros.org/wiki/ros_arduino_firmware</url>
<buildtool_depend>catkin</buildtool_depend>
</package>

View File

@ -1,30 +1,23 @@
cmake_minimum_required(VERSION 2.4.6) cmake_minimum_required(VERSION 2.8.3)
include($ENV{ROS_ROOT}/core/rosbuild/rosbuild.cmake) project(ros_arduino_msgs)
# Set the build type. Options are: find_package(catkin REQUIRED genmsg std_msgs)
# Coverage : w/ debug symbols, w/o optimization, w/ code-coverage
# Debug : w/ debug symbols, w/o optimization
# Release : w/o debug symbols, w/ optimization
# RelWithDebInfo : w/ debug symbols, w/ optimization
# MinSizeRel : w/o debug symbols, w/ optimization, stripped binaries
#set(ROS_BUILD_TYPE RelWithDebInfo)
rosbuild_init() add_message_files(FILES
AnalogFloat.msg
Analog.msg
Digital.msg
SensorState.msg
)
#set the default path for built executables to the "bin" directory add_service_files(FILES
set(EXECUTABLE_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/bin) DigitalSetDirection.srv
#set the default path for built libraries to the "lib" directory DigitalWrite.srv
set(LIBRARY_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/lib) ServoRead.srv
ServoWrite.srv
)
#uncomment if you have defined messages generate_messages(DEPENDENCIES std_msgs)
rosbuild_genmsg()
#uncomment if you have defined services catkin_package(DEPENDS std_msgs)
rosbuild_gensrv()
#common commands for building c++ executables and libraries
#rosbuild_add_library(${PROJECT_NAME} src/example.cpp)
#target_link_libraries(${PROJECT_NAME} another_library)
#rosbuild_add_boost_directories()
#rosbuild_link_boost(${PROJECT_NAME} thread)
#rosbuild_add_executable(example examples/example.cpp)
#target_link_libraries(example ${PROJECT_NAME})

View File

@ -1 +0,0 @@
include $(shell rospack find mk)/cmake.mk

View File

@ -1,26 +0,0 @@
/**
\mainpage
\htmlinclude manifest.html
\b ros_arduino_msgs is ...
<!--
Provide an overview of your package.
-->
\section codeapi Code API
<!--
Provide links to specific auto-generated API documentation within your
package that is of particular interest to a reader. Doxygen will
document pretty much every part of your code, so do your best here to
point the reader to the actual API.
If your codebase is fairly large or has different sets of APIs, you
should use the doxygen 'group' tag to keep these APIs together. For
example, the roscpp documentation has 'libros' group.
-->
*/

View File

@ -1,13 +0,0 @@
<package>
<description brief="ros_arduino_msgs">
ROS Arduino Messages
</description>
<author>Patrick Goebel</author>
<license>BSD</license>
<review status="unreviewed" notes=""/>
<url>http://ros.org/wiki/ros_arduino_msgs</url>
</package>

View File

@ -0,0 +1,17 @@
<package>
<name>ros_arduino_msgs</name>
<version>0.2.0</version>
<description>
ROS Arduino Messages.
</description>
<author>Patrick Goebel</author>
<maintainer email="patrick@pirobot.org">Patrick Goebel</maintainer>
<license>BSD</license>
<url>http://ros.org/wiki/ros_arduino_msgs</url>
<buildtool_depend>catkin</buildtool_depend>
<build_depend>std_msgs</build_depend>
<run_depend>std_msgs</run_depend>
</package>

View File

@ -1,30 +1,18 @@
cmake_minimum_required(VERSION 2.4.6) cmake_minimum_required(VERSION 2.8.3)
include($ENV{ROS_ROOT}/core/rosbuild/rosbuild.cmake) project(ros_arduino_python)
# Set the build type. Options are: find_package(catkin REQUIRED)
# Coverage : w/ debug symbols, w/o optimization, w/ code-coverage catkin_package(DEPENDS)
# Debug : w/ debug symbols, w/o optimization catkin_python_setup()
# Release : w/o debug symbols, w/ optimization
# RelWithDebInfo : w/ debug symbols, w/ optimization
# MinSizeRel : w/o debug symbols, w/ optimization, stripped binaries
#set(ROS_BUILD_TYPE RelWithDebInfo)
rosbuild_init() install(DIRECTORY config
DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
)
#set the default path for built executables to the "bin" directory install(DIRECTORY launch
set(EXECUTABLE_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/bin) DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
#set the default path for built libraries to the "lib" directory )
set(LIBRARY_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/lib)
#uncomment if you have defined messages install(DIRECTORY nodes
#rosbuild_genmsg() DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
#uncomment if you have defined services )
#rosbuild_gensrv()
#common commands for building c++ executables and libraries
#rosbuild_add_library(${PROJECT_NAME} src/example.cpp)
#target_link_libraries(${PROJECT_NAME} another_library)
#rosbuild_add_boost_directories()
#rosbuild_link_boost(${PROJECT_NAME} thread)
#rosbuild_add_executable(example examples/example.cpp)
#target_link_libraries(example ${PROJECT_NAME})

View File

@ -1 +0,0 @@
include $(shell rospack find mk)/cmake.mk

View File

@ -1,26 +0,0 @@
/**
\mainpage
\htmlinclude manifest.html
\b ros_arduino_python is ...
<!--
Provide an overview of your package.
-->
\section codeapi Code API
<!--
Provide links to specific auto-generated API documentation within your
package that is of particular interest to a reader. Doxygen will
document pretty much every part of your code, so do your best here to
point the reader to the actual API.
If your codebase is fairly large or has different sets of APIs, you
should use the doxygen 'group' tag to keep these APIs together. For
example, the roscpp documentation has 'libros' group.
-->
*/

View File

@ -1,22 +0,0 @@
<package>
<description brief="ros_arduino_python">
ROS Arduino Python
</description>
<author>Patrick Goebel</author>
<license>BSD</license>
<review status="unreviewed" notes=""/>
<url>http://ros.org/wiki/ros_arduino_python</url>
<depend package="roscpp"/>
<depend package="rospy"/>
<depend package="std_msgs"/>
<depend package="sensor_msgs"/>
<depend package="geometry_msgs"/>
<depend package="nav_msgs"/>
<depend package="tf"/>
<depend package="ros_arduino_msgs"/>
</package>

View File

@ -21,10 +21,10 @@
import roslib; roslib.load_manifest('ros_arduino_python') import roslib; roslib.load_manifest('ros_arduino_python')
import rospy import rospy
from arduino_driver import Arduino from ros_arduino_python.arduino_driver import Arduino
from arduino_sensors import * from ros_arduino_python.arduino_sensors import *
from ros_arduino_msgs.srv import * from ros_arduino_msgs.srv import *
from base_controller import BaseController from ros_arduino_python.base_controller import BaseController
from geometry_msgs.msg import Twist from geometry_msgs.msg import Twist
import os, time import os, time
import thread import thread

View File

@ -0,0 +1,21 @@
<package>
<name>ros_arduino_python</name>
<version>0.2.0</version>
<description>
ROS Arduino Python.
</description>
<author>Patrick Goebel</author>
<maintainer email="patrick@pirobot.org">Patrick Goebel</maintainer>
<license>BSD</license>
<url>http://ros.org/wiki/ros_arduino_python</url>
<buildtool_depend>catkin</buildtool_depend>
<run_depend>rospy</run_depend>
<run_depend>std_msgs</run_depend>
<run_depend>sensor_msgs</run_depend>
<run_depend>geometry_msgs</run_depend>
<run_depend>nav_msgs</run_depend>
<run_depend>tf</run_depend>
<run_depend>ros_arduino_msgs</run_depend>
</package>

View File

@ -0,0 +1,11 @@
#!/usr/bin/env python
from distutils.core import setup
from catkin_pkg.python_setup import generate_distutils_setup
d = generate_distutils_setup(
packages=['ros_arduino_python'],
package_dir={'': 'src'},
)
setup(**d)

View File

@ -1,12 +0,0 @@
<stack>
<description brief="ros_arduino_bridge">ROS Arduino Bridge</description>
<author>Maintained by Patrick Goebel</author>
<license>BSD</license>
<review status="unreviewed" notes=""/>
<url>http://ros.org/wiki/ros_arduino_bridge</url>
<depend stack="ros" />
<depend stack="ros_comm" /> <!-- std_srvs, rospy, roscpp -->
<depend stack="common_msgs" /> <!-- nav_msgs, geometry_msgs, sensor_msgs, diagnostic_msgs -->
<depend stack="geometry" /> <!-- tf -->
</stack>