Quantcast
Channel: ROS Answers: Open Source Q&A Forum - RSS feed
Viewing all articles
Browse latest Browse all 152

Strange behavior of xacro namespaced include

$
0
0
Hi all, I don't know if it is a bug or the default behavior, but I was using the [_namespaced include_](http://wiki.ros.org/xacro#Including_other_xacro_files) for the first time and I am a bit confused. I have done something like the following to avoid name clashes: However it turns out that the name clashes still exist: unknown macro name: xacro:build_model_part XacroException(u'unknown macro name: xacro:build_model_part',) where `build_model_part` is another macro called inside the two utility files. The only workaround that I found is to add the namespace inside _my_macros_1.xacro_ (using `my_namespace_1`) and _my_macros_2.xacro_ (using `my_namespace_2`) to every single macro call. This obviously avoid name clashes, but I would have called the macros respectively `build_model_1` and `build_model_2` instead of applying the namespace inside all the calls... Where is my mistake?

Viewing all articles
Browse latest Browse all 152

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>