Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

panda_eus build failure with xacro=1.13.11 #1758

Closed
knorth55 opened this issue Dec 6, 2022 · 8 comments
Closed

panda_eus build failure with xacro=1.13.11 #1758

knorth55 opened this issue Dec 6, 2022 · 8 comments

Comments

@knorth55
Copy link
Member

knorth55 commented Dec 6, 2022

___________________________________________________________________________________________________________________________________________________________________________________________________________
Errors     << panda_eus:make /home/fetch/ros/melodic/logs/panda_eus/build.make.001.log                                                                                                                     
xacro: in-order processing became default in ROS Melodic. You can drop the option.
name 'xacro' is not defined 
when evaluating expression 'xacro.load_yaml('$(find franka_description)/robots/panda/joint_limits.yaml')'
when processing file: dual_panda.urdf.xacro
make[2]: *** [/home/fetch/ros/melodic/src/jsk-ros-pkg/jsk_robot/jsk_panda_robot/panda_eus/models/dual_panda.urdf] Error 2
make[2]: *** Deleting file '/home/fetch/ros/melodic/src/jsk-ros-pkg/jsk_robot/jsk_panda_robot/panda_eus/models/dual_panda.urdf'
make[1]: *** [CMakeFiles/generate_panda_lisp.dir/all] Error 2
make: *** [all] Error 2
cd /home/fetch/ros/melodic/build/panda_eus; catkin build --get-env panda_eus | catkin env -si  /usr/bin/make --jobserver-fds=6,7 -j; cd -
...........................................................................................................................................................................................................
Failed     << panda_eus:make                    [ Exited with code 2 ]                                                                                                                                     
Failed    <<< panda_eus                         [ 1.5 seconds ]    
@knorth55
Copy link
Member Author

knorth55 commented Dec 6, 2022

this error happens xacro 1.13.11.
I update xacro to 1.13.18, it works.

@knorth55
Copy link
Member Author

knorth55 commented Dec 6, 2022

we need this PR to use xacro.load_yaml.
xacro>=1.13.14 is required to build panda_eus.

ros/xacro#283

@knorth55 knorth55 changed the title panda_eus build failure with xacro panda_eus build failure with xacro=1.13.11 Dec 6, 2022
@pazeshun
Copy link
Contributor

pazeshun commented Dec 6, 2022

そうです、xacroの問題があったので、melodic未満ではdual_panda.lを生成しないように書きました。

# xacro.load_yaml cannot be recognized under melodic, while it is recommended on melodic and upper.
# PR introducing xacro.load_yaml: https://github.com/ros/xacro/pull/283
# Related issue: https://github.com/ros/xacro/issues/298

この時は、franka_descriptionのバージョンを書かなかったように、パッケージをaptの最新にしておくのはユーザーの責任という思想でしたが、franka_descriptionのバージョンをCMakeLists.txtに書くなら、xacroのバージョンもCMakeLists.txtに書いた方がいい気もしてきたので、やっておきます。

なお、xacro.load_yamlを使っているのはfranka_descriptionもなので、franka_descriptionを最新にした時にxacroも最新になる、というのが理想的なあり方ではありますが、現状それを簡単に実現する仕組みはないように思われます。
https://github.com/frankaemika/franka_ros/blob/0.10.1/franka_description/robots/panda/panda.urdf.xacro#L9

@pazeshun
Copy link
Contributor

pazeshun commented Dec 6, 2022

#1751 でxacroのバージョンを明示的にチェックするようにしました

@knorth55
Copy link
Member Author

knorth55 commented Dec 7, 2022

#1751 確認しました.OKです.
xacroを最新にし忘れていたときのエラーがわかりにくいので,最新版にすべきという話と,エラーがわかりにくい話は別だと思います.

@pazeshun
Copy link
Contributor

pazeshun commented Dec 7, 2022

それなら、「エラーがわかりにくい」と明示的に書いてほしかったです。
今回はたまたま直せてましたが

@knorth55
Copy link
Member Author

knorth55 commented Dec 7, 2022

あ,個人的には最新版にすべきであるというのは,全員そうすべきであるとは思わないです.
実際xacroが先に入っていたらrosdepしても,upgradeされないので,自分でapt upgradeしないといけないのは,なかなか難しい気がします.
ただ長谷川の意見を聞き入れたとしても,エラーがわかりにくい話は残るなと思っています.

@pazeshun
Copy link
Contributor

Closed via #1751

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants