ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Trouble with winros installation

asked 2013-04-17 23:13:59 -0600

ChrisEule gravatar image

updated 2014-01-28 17:16:15 -0600

ngrennan gravatar image

Hello guys,

I'm trying to install winros on Windows 7 (64 Bit) and have some trouble with the step "winros sdk configure" like described in http://www.ros.org/wiki/win_ros/Msvc%20Build%20Environment%20-%20Fuerte. This is my console output:

"Configuring the build"

-- +++ catkin
-- Using CATKIN_DEVEL_PREFIX: C:/work/build_sdk/devel
-- Using CMAKE_PREFIX_PATH: C:/work/build_sdk;C:/work/build_sdk/cmake
CMake Warning at catkin/cmake/test/gtest.cmake:99 (message):
  gtest not found, C++ tests can not be built.  You can run 'svn checkout
  http://googletest.googlecode.com/svn/tags/release-1.6.0 gtest' in the root
  of your workspace
Call Stack (most recent call first):
  catkin/cmake/all.cmake:133 (include)
  catkin/CMakeLists.txt:8 (include)


-- Using CATKIN_TEST_RESULTS_DIR: C:/work/build_sdk/test_results
-- catkin 0.5.65
-- BUILD_SHARED_LIBS is on
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~  traversing 32 packages in topological order:
-- ~~  - ros_comm (metapackage)
-- ~~  - rosconsole
-- ~~  - rosgraph
-- ~~  - rosgraph_msgs
-- ~~  - roslaunch
-- ~~  - rosmaster
-- ~~  - rosmsg
-- ~~  - rospack
-- ~~  - rosparam
-- ~~  - rospy
-- ~~  - rosservice
-- ~~  - rostest
-- ~~  - std_srvs
-- ~~  - test_roslib_comm
-- ~~  - xmlrpcpp
-- ~~  - roscpp
-- ~~  - rosout
-- ~~  - actionlib
-- ~~  - message_filters
-- ~~  - rosnode
-- ~~  - rostopic
-- ~~  - roswtf
-- ~~  - test_roscpp
-- ~~  - test_rosgraph
-- ~~  - test_roslaunch
-- ~~  - test_rosmaster
-- ~~  - test_rosparam
-- ~~  - test_rospy
-- ~~  - test_rosservice
-- ~~  - topic_tools
-- ~~  - rosbag
-- ~~  - test_rosbag
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ processing catkin metapackage: 'ros_comm'
-- ==> add_subdirectory(ros_comm/ros_comm)
CMake Error at ros_comm/ros_comm/CMakeLists.txt:3 (find_package):
  Could not find module Findcatkin.cmake or a configuration file for package
  catkin.

  Adjust CMAKE_MODULE_PATH to find Findcatkin.cmake or set catkin_DIR to the
  directory containing a CMake configuration file for catkin.  The file will
  have one of the following names:

    catkinConfig.cmake
    catkin-config.cmake



-- +++ processing catkin package: 'rosconsole'
-- ==> add_subdirectory(ros_comm/tools/rosconsole)
CMake Error at ros_comm/tools/rosconsole/CMakeLists.txt:4 (find_package):
  Could not find module Findcatkin.cmake or a configuration file for package
  catkin.

  Adjust CMAKE_MODULE_PATH to find Findcatkin.cmake or set catkin_DIR to the
  directory containing a CMake configuration file for catkin.  The file will
  have one of the following names:

    catkinConfig.cmake
    catkin-config.cmake



CMake Error at ros_comm/tools/rosconsole/CMakeLists.txt:12 (message):
  Couldn't find log4cxx library


-- Configuring incomplete, errors occurred!

"You may now proceed with 'winros sdk build'"

The Problem is that there is only a "catkinConfig.cmake" in directory C:\work\build_sdk\catkin\catkin_generated\installspace but I'm guessing that this is not the right one because that file will be created by the build process which is started with "winros sdk configure". The advise to adjust CMAKE_MODULE_PATH to find Findcatkin.cmake is also not working for me because there exists no Findcatkin.cmake.

Has somebody experience with that problem?

Thanks

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
2

answered 2013-05-06 22:03:28 -0600

Daniel Stonier gravatar image

Glad to see you got it working.

The navigation stack won't work out of the box - it's got a few dependencies we haven't ported yet (porting is a bit painful, not only the usual cross platform bugs, but each package needs to implement all of the windows declspec macros).

It's not too hard and I'm looking forward to the day people start porting some of the ros stacks themselves (some early notes here), but for now, the winros builds are primarily intended as a way to link your linux robot to the windows world, or a windows based driver.

Ubuntu virtual machine sounds like the way to go for you.

edit flag offensive delete link more

Comments

Thank you very much for your quick reply. I think I will go back to Ubuntu

ChrisEule gravatar image ChrisEule  ( 2013-05-07 03:01:44 -0600 )edit

@Daniel How do you appraise the work to port a stack like the navigation? Isn't it very hard and lots of work because of all the package dependencies?

ChrisEule gravatar image ChrisEule  ( 2013-05-14 04:15:42 -0600 )edit

It will still be easier and better running a 'linux ros robot' for many reasons. Because of this we're generally avoiding robot stacks and just working on those which will let you link and work with a 'linux ros robot'. e.g. rqt, tf etc.

Daniel Stonier gravatar image Daniel Stonier  ( 2013-05-19 13:39:50 -0600 )edit
0

answered 2013-05-06 21:28:27 -0600

ChrisEule gravatar image

updated 2013-05-06 21:29:32 -0600

Well, I decided to follow this Tutorial page: http://ros.org/wiki/win_ros/groovy/Msvc%20Compiled%20SDK

It's nearly the same but you have to compile ROS on Windows yourself with the Visual Studio Compiler. It worked for me very well (Windows 7, 64 Bit) but make sure you have a clean Installation of Visual Studio. If you get a compile error like "error LNK2038: mismatch detected for '_MSC_VER': value '1600' doesn't match value '1700'" you maybe have trouble with libraries from another Visual Studio version.

So win_ros is running on my machine but now I want to navigate my robot. Is there a navigation stack that I'm able to compile on Windows because I think I can't simply use that one http://www.ros.org/wiki/navigation. Or do I have to use an Ubuntu VM which is running the navigation and communicating with my win_ros nodes?

edit flag offensive delete link more

Comments

Nope, you can give compiling the nav stack for Windows a shot, but I would be surprised if there were not issues to work out. Right now, I think the out-of-the-box usability on Windows is limited to ros communication for use with GUI's and Windows only drivers.

William gravatar image William  ( 2013-05-14 08:41:36 -0600 )edit

Question Tools

Stats

Asked: 2013-04-17 23:13:59 -0600

Seen: 1,160 times

Last updated: May 06 '13