Merge pull request #1 from mars-uoit/travis

Added Travis CI and roslaunch check.

Author: mikehosmar

.travis.yml

@@ -0,0 +1,29 @@
+sudo: required
+dist: trusty
+language: generic
+compiler:
+  - gcc
+  - clang
+env:
+  - CC=gcc CXX=g++
+  - CC=clang CXX=clang++
+install:
+  - export CI_ROS_DISTRO=indigo
+  - sudo sh -c 'echo "deb http://packages.ros.org/ros-shadow-fixed/ubuntu trusty main" > /etc/apt/sources.list.d/ros-latest.list'
+  - wget http://packages.ros.org/ros.key -O - | sudo apt-key add -
+  - sudo apt-get update
+  - sudo apt-get install python-rosdep -y
+  - sudo `which rosdep` init
+  - rosdep update
+  - rosdep install --default-yes --from-paths . --ignore-src --rosdistro $CI_ROS_DISTRO
+script:
+  - mkdir -p ~/catkin_ws/src
+  - ln -s $TRAVIS_BUILD_DIR ~/catkin_ws/src/repo
+  - cd ~/catkin_ws
+  - source /opt/ros/$CI_ROS_DISTRO/setup.bash
+  - catkin_make
+  - catkin_make run_tests
+  - catkin_test_results .
+  - catkin_make install
+notifications:
+  email: false

CMakeLists.txt

@@ -98,7 +98,7 @@ catkin_package(
 include_directories(
   include
   ${catkin_INCLUDE_DIRS}
-  ${Boost_INCLUDE_DIRS} 
+  ${Boost_INCLUDE_DIRS}
 )
 
 ## Declare a cpp library
@@ -171,11 +171,7 @@ target_link_libraries(ursa_node
 ## Testing ##
 #############
 
-## Add gtest based cpp test target and link libraries
-# catkin_add_gtest(${PROJECT_NAME}-test test/test_ursa_driver.cpp)
-# if(TARGET ${PROJECT_NAME}-test)
-#   target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME})
-# endif()
-
-## Add folders to be run by python nosetests
-# catkin_add_nosetests(test)
+if (CATKIN_ENABLE_TESTING)
+  find_package(roslaunch REQUIRED)
+  roslaunch_add_file_check(launch/ursa_node.launch)
+endif()

README.md

@@ -1,4 +1,4 @@
-URSAII Driver
+URSAII Driver [![Build Status](https://travis-ci.org/mars-uoit/URSAII-Driver.svg)](https://travis-ci.org/mars-uoit/URSAII-Driver)
 =============
 Version 0.1.0
 
@@ -10,15 +10,15 @@ This software will allow you to get radiation measurements in either gross count
 
 ###C++ Library###
 I tried to make the driver portion of the repo as stand-alone as possible. I exposes functions to execute any of the commands that URSA will respond to.  Keep in mind though that some commands are meant to only be executed by factory personnel and setting parameters in a incorrect manner could damage the URSA or the detector head. Check out the doxygen documentation for the ursa::Interface class.
-  
+
 ####Note####
-If you are familiar with the standard software provided to operate the URSA there is a major difference between that software and this; This software will only provide you with the raw readings from URSA, if energy calibration or any other conditioning must be done you must implement it in your project. 
+If you are familiar with the standard software provided to operate the URSA there is a major difference between that software and this; This software will only provide you with the raw readings from URSA, if energy calibration or any other conditioning must be done you must implement it in your project.
 
 
 
 ## How do I get set up? ##
 
-The ROS node can be compiled in a catkin workspace and its dependencies can be installed with rosdep. The Library depends on several boost libraries and William Woodall's serial library.  The Library can be compiled and installed using the Makefile (TODO). 
+The ROS node can be compiled in a catkin workspace and its dependencies can be installed with rosdep. The Library depends on several boost libraries and William Woodall's serial library.  The Library can be compiled and installed using the Makefile (TODO).
 
 
 ###Contact###

package.xml

@@ -8,41 +8,25 @@
 
   <license>MIT</license>
 
-  <!-- Url tags are optional, but mutiple are allowed, one per tag -->
-  <!-- Optional attribute type can be: website, bugtracker, or repository -->
-  <!-- Example: -->
   <!-- <url type="website">http://wiki.ros.org/ursa_driver</url> -->
 
   <author email="[email protected]">Mike Hosmar</author>
 
-
-  <!-- The *_depend tags are used to specify dependencies -->
-  <!-- Dependencies can be catkin packages or system dependencies -->
-  <!-- Examples: -->
-  <!-- Use build_depend for packages you need at compile time: -->
-  <!--   <build_depend>message_generation</build_depend> -->
-  <!-- Use buildtool_depend for build tool packages: -->
-  <!--   <buildtool_depend>catkin</buildtool_depend> -->
-  <!-- Use run_depend for packages you need at runtime: -->
-  <!--   <run_depend>message_runtime</run_depend> -->
-  <!-- Use test_depend for packages you need only for testing: -->
-  <!--   <test_depend>gtest</test_depend> -->
   <buildtool_depend>catkin</buildtool_depend>
+
   <build_depend>roscpp</build_depend>
   <build_depend>serial</build_depend>
   <build_depend>std_msgs</build_depend>
   <build_depend>std_srvs</build_depend>
   <build_depend>message_generation</build_depend>
+  <build_depend>boost</build_depend>
+  <build_depend>roslaunch</build_depend>
+
   <run_depend>roscpp</run_depend>
   <run_depend>serial</run_depend>
   <run_depend>std_msgs</run_depend>
   <run_depend>std_srvs</run_depend>
   <run_depend>message_runtime</run_depend>
+  <run_depend>boost</run_depend>
 
-
-  <!-- The export tag contains other, unspecified, tags -->
-  <export>
-    <!-- Other tools can request additional information be placed here -->
-
-  </export>
 </package>