Just curious - as the willow garage guys have mentioned elsewhere, seems that the major hurdle is the build system. I&#39;m wondering how hard it would be to do windows development with an ubuntu mingw toolchain.<br><br>I&#39;ve tested cross-compiling with a partially crossed ros (native linux ros building non-ros cross-compiled packages), and that seems to work no problem. I wonder how hard it would be to go the extra step and do a full cross with mingw (i.e. just basic stuff, roscpp, roslib etc). And how well does mingw work with win7?<br>
<br>Regards,<br>Daniel Stonier<br><br><div class="gmail_quote">On 22 August 2010 17:17, Christian Verbeek <span dir="ltr">&lt;<a href="mailto:verbeek@servicerobotics.eu">verbeek@servicerobotics.eu</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Dear all,<br>
<br>
I would like to come back to the problem of communicating with a ROS<br>
system from windows. Especially in commercial applications it is highly<br>
appreciable to have a GUI for controlling, visualisation and<br>
parametrisation running on a Windows host as 99% of customers in<br>
industry run Windows. What ever one might think about this - its a fact<br>
and can not be ignored. The robot itself is equipped with a powerful<br>
Linux system running the whole ROS system.<br>
<br>
It is true that setting up a bridge from ROS to some other middle-ware<br>
like Ice is straight forward. On the other hand system complexity<br>
increases a lot when using a bridge. Also at least in the case of Ice<br>
licensing is a big issue when talking about commercial applications. The<br>
Ice license is extremely restrictive (and expensive).<br>
<br>
Some time ago I read about the intention to make roslib and roscpp OS<br>
independent. Is this really a big issue? In the situation described<br>
above one might need only a subset of the overall functionality.<br>
Starting in September 2010 I will have a trainee who&#39;s job will be to<br>
shed some light on this ROS-Windows stuff. Maybe we can discuss the<br>
steps to get roslib and roscpp compiling on Windows (using Visual Studio<br>
2008 or later). Maybe someone started to work in this direction and can<br>
give some hints.<br>
<br>
Regards<br>
Christian<br>
<br>
_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Phone : +82-10-5400-3296 (010-5400-3296)<br>Home: <a href="http://snorriheim.dnsdojo.com/">http://snorriheim.dnsdojo.com/</a><br>Yujin Robot: <a href="http://www.yujinrobot.com/">http://www.yujinrobot.com/</a><br>
Embedded Control Libraries: <a href="http://snorriheim.dnsdojo.com/redmine/wiki/ecl">http://snorriheim.dnsdojo.com/redmine/wiki/ecl</a><br>