[ros-users] communicating with windows

Tue Oct 5 03:52:46 UTC 2010

Having rosmaster and other tools like rviz would be nice, but this is a huge
step in the right direction, just being able, like Christian said, to
deliver Windows GUI's that can natively communicate with a robot running ROS
gives us a lot a justification ammo when trying to convince others to adopt.

Also, if you have any questions about what I've done so far while trying to
get vs2010 support let me know, though I doubt it will give you guys any
trouble given the quality of work so far.

Thanks, this is really useful!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
William Woodall
Graduate Software Engineering
Auburn University
w at auburn.edu
wjwwood at gmail.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Mon, Oct 4, 2010 at 2:53 PM, Josh Faust <jfaust at willowgarage.com> wrote:

> For development though it's nice to be able to run just against your local
> system, without a needing a separate box (or vm).
>
> Josh
>
>
> On Mon, Oct 4, 2010 at 11:43 AM, Christian Verbeek <
> verbeek at servicerobotics.eu> wrote:
>
>>  Earlier in this thread I pointed out that my intention is to be able to
>> create shiny windows GUIs while the robot runs Linux and the whole ROS
>> system. Running a rosmaster on windows would mean that you try to run
>> your robot with windows? Not a good idea if you ask me.
>>
>> The windows GUI is asked by our customers from which 99% use windows and
>> do not want to use anything else. Bringing ROS to industry means ROS
>> hits windows. But the robot itself can run Linux as nobody is interested
>> in what is going on in the machine (as long as it is working).
>>
>> Am 04.10.2010 17:54, schrieb Ken Conley:
>> > FYI: it would probably be good to start generating patches for these
>> > changes soon. When we begin work on REP 100 (soon), there will be a
>> > lot of changes to the underlying ROS code base.
>> >
>> > Feel free to update the Windows wiki page. In fact, it might be better
>> > to host the instructions on the ROS.org wiki itself so that other
>> > users can continue to contribute updates as they have on this e-mail
>> > thread.
>> >
>> > Also, I noticed that you require a separate Linux install to use the
>> > rosmaster -- what's the integration issue here? We've previously had
>> > people use the rosmaster on Windows just by changing the path loader
>> > (roslib.load_manifest). Assuming that rospack is accessible, it should
>> > be even easier to use the rosmaster, so I'm curious as to what the
>> > issues are. I know that the roscore can't be run on Windows due to
>> > roslaunch, but rosmaster can be run separately.
>> >
>> >  - Ken
>> >
>> > On Mon, Oct 4, 2010 at 2:46 AM, Christian Verbeek
>> > <verbeek at servicerobotics.eu> wrote:
>> >> We made a ROS WIN32 web-page.
>> >>
>> >> http://www.servicerobotics.eu/index.php?id=37&L=2
>> >>
>> >> We also provide a binary distribution in form of a windows installer
>> and
>> >> examples how to use it. You might like to link our web-page this into
>> your
>> >> wiki.
>> >>
>> >> http://www.ros.org/wiki/cturtle/Installation/Windows
>> >>
>> >> From my point of view our work is the first approach that is really
>> usable
>> >> for windows development. We will add Visual Studio 2010 support within
>> the
>> >> next weeks.
>> >>
>> >> Regards
>> >> Christian
>> >>
>> >> Am 01.10.2010 22:35, schrieb Josh Faust:
>> >>> I have now run into another problem, I am getting lots of linking
>> errors
>> >>> related to xmlrpc++, which make me think that it is an incompatibility
>> with
>> >>> vs2010, because this is the same type of exceptions I got from log4cxx
>> >>> before I found a vs2010 compatibility fix on a forum (see my previous
>> >>> email).  However, xmlrpc++ hasn't been updated on sf since 2003 and I
>> am not
>> >>> finding anything about these problems or even anything related to
>> vs2010 and
>> >>> xmlrpcpp.  Here are the exceptions: http://pastry.se/1041001/.  I
>> have
>> >>> downloaded the source for xmlrpc++ and tried to compile it with
>> vs2010, but
>> >>> when converting the .sln's to vs2010 all of them failed to convert for
>> some
>> >>> reason or another, I haven't had time to investigate this issue yet.
>> >> The version of xmlrpc++ we use is heavily modified, so you need to use
>> the
>> >> source from the ROS package.  It looks like it's included in that svn
>> repo,
>> >> under cturtle/3rdparty
>> >> Josh
>> >>
>> >> _______________________________________________
>> >> ros-users mailing list
>> >> ros-users at code.ros.org
>> >> https://code.ros.org/mailman/listinfo/ros-users
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> ros-users mailing list
>> >> ros-users at code.ros.org
>> >> https://code.ros.org/mailman/listinfo/ros-users
>> >>
>> >>
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users at code.ros.org
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users at code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>
>
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20101004/70209a48/attachment-0003.html>