-
Notifications
You must be signed in to change notification settings - Fork 552
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
[ros2] General ros2 maintenance and Humble support #373
Comments
First PR for both |
Updated PR (never merged) for costmap_converter: rst-tu-dortmund/costmap_converter#27 |
Hi @doisyg . I checked out your branch (great work btw, thanks) and tested it on a ROS2 docker container -- everything seems to be working as expected. How can we move forward to make this "official"? Considering TEB is mentioned as one of the controller plugins for Nav2, I think having an up to date release would be important. |
Hi @davidteixeira, I don't really know, we need somebody with admin rights. Last time (galactic) @SteveMacenski gave us a hand for merging but we did not make an official release. |
I was given permissions for merging PRs and making new branches, etc but I don't have the time to take on maintaining this codebase. TEB is very complex and I don't have the cycles to add something of this size to my queue. Really, at most I can be a rubber stamp if there's a trusted agent with a well tested PR, but if major changes are made and stuff breaks, I'm not going to really be able to do anything about it. I have made a I don't have rights over costmap converter though 😦 |
I recently run TEB with Humble w/o problems. Please ensure that you are using latest ros2-master branch, as we have recently merged PR #371 that fixes compilation issues |
Additional, this more complete PR is ready and is going to be merged soon: #374 |
TEB and nav2 are working well together under ros2 Humble (ros2-master branch that you have to compile from source). That was the point of this recent PR: #374 There is not provided launch files for the ROS2 Humble versions and the readme is outdated. |
I'm trying to build teb_local_planner from source on Nvidia Xavier Humble (it's Ubuntu 18 but that should not be causing my problem). I cannot install libg2o (ros-humble-libg2o) from apt so I need to build it from source, which I do successfully:
it's this tag (release/humble/libg2o/2020.5.29-4), which I believe is the right one as it is the one installed via apt on Ubuntu 20. My problem is that when building teb_local_planner, I get:
Any help would be appreciated. |
https://github.com/ros/rosdistro/blob/master/humble/distribution.yaml#L2097 this is the version in rosdep, you might want to see if those are the same. |
it is indeed:
I also edited the building logs in my first post (added some debug) to show that libg2o was in fact found:
This question might be related but I'm really a noob when it comes to cmake |
If you look at your install, can you find that header? |
you're referring to the header from the error right? -> misc.h. If so then yes it's there |
Is that simply the first header in the files that its complaining about from g2o? Maybe it has nothing to do with that file, but just finding any file in g2o. (This is me just going through what I would do if I ran into this issue, this isn't any specific insight about g2o, don't mean to state the obvious) |
Yes I think this was the problem. I built and installed g2o with |
Afaik all works now on both humble and jazzy, so we can close this |
Hello TEB users,
I did not come here for a long time, but it seems that the
noetic
branch have seen lots of activity (@corot , @kenomo , @siferati ).I believe there is a sync that needs to be done with the
ros2-master
branch, and also theros2-master
branch needs changes to work withhumble
(@chenjunn) , @tonynajjar).I have already a
humble
version that works with the last nav2 (#371) plus some changes that I never pushed for dynamic footprint support (@guilyx). I am willing to contribute an push these changes in the following days.I propose that all parties interested discuss here how to get organized. Who has the maintenance rights nowadays ? I believe a first step should be to create a
galactic
branch from a copy of the currentros2-master
. Then maybe ahumble
androlling
branch , or we continue to useros2-master
?The text was updated successfully, but these errors were encountered: