So I'm not sure what all the cmake-wizardry is trying to do in xacro-extras.cmake, but it appears the problem here is actually that xacro.py in <install>/lib/xacro/ is not executable as it would be if it were brought in via a "install(PROGRAMS ..." type of cmake command.

As a temporary fix, you can make /opt/ros/groovy/install/lib/xacro/xacro.py executable and your existing launch files will work again until a patch gets out

I opened a ticket here: https://github.com/ros/xacro/issues/1

-Fergs

On Mon, Mar 4, 2013 at 3:42 AM, Michael Gratton <mikeg@cse.unsw.edu.au> wrote:
On 04/03/13 21:37, Tully Foote wrote:
> ros-groovy-xacro : 1.6.1 -> 1.7.2

xacro seems to be newly catkinised, which unless I am missing something
means `rosrun xacro xacro.py` will no longer work?

If so, that might break a whole lot of existing Groovy setups, like mine
did just then.

//Mike

--
Michael Gratton <http://www.cse.unsw.edu.au/~mikeg/>
UNSW School of Computer Science and Engineering.



_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users