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

Release ros2 version for ROS2 iron #439

Closed
Rayman opened this issue Jan 16, 2024 · 12 comments
Closed

Release ros2 version for ROS2 iron #439

Rayman opened this issue Jan 16, 2024 · 12 comments

Comments

@Rayman
Copy link
Contributor

Rayman commented Jan 16, 2024

On Ubuntu 2022.04 when you install ros-iron-pcl-ros you still get the ROS1 version (2.4.0). Can you release the ros2 branch on iron?

@Timple
Copy link

Timple commented Jan 16, 2024

It's only the include <ros/ros.h> which is ros1. So a new bloom release which includes this fix: #410 should do it.

@Timple
Copy link

Timple commented Jan 16, 2024

Actually, the ros2 branch seems to be a half-port.

For example this line: https://github.com/ros-perception/perception_pcl/blob/ros2/pcl_ros/include/pcl_ros/point_cloud.hpp#L155

sensor_msgs::PointCloud2

Should be

sensor_msgs::msg::PointCloud2

So I don't think this file has worked for anyone on ros2 yet.

@SteveMacenski
Copy link
Member

SteveMacenski commented Jan 16, 2024

This repo is not fully ported to ROS 2, this is true. Type masqerading was never fully implemented (mostly because masqerading didn't exist for a long time). You can see a number of things are commented out and not being compiled [1]

[1] https://github.com/ros-perception/perception_pcl/blob/ros2/pcl_ros/CMakeLists.txt

@mvieth
Copy link
Contributor

mvieth commented Jan 17, 2024

There is a pull request which fixes the types on the ros2 branch: #425

@shu-beg
Copy link

shu-beg commented Feb 26, 2024

Is there any update regarding the release of already ported features? I had a short look into perception_pcl-release and it seems as there was an attempt to release at least 2.4.1 but for humble / iron / rolling there is still only 2.4.0 available as debian? Anyways, as there are quite useful features available on ros2 branch compared to 2.4.1 (e.g. filters) I would really appreciate a new release.

@SteveMacenski
Copy link
Member

Figuring it out now, I'm rolling back locally the ros2 branch to the last sync and branching off humble / iron and going to roll forward those commits that are API/ABI compatiable and then run a sync over those with the subset of ros2 changes that are appropriate. I'll also update Rolling.

Currently in progress.

@SteveMacenski
Copy link
Member

My apologies, I'm not sure how this fell so far off my radar for so long

@Rayman
Copy link
Contributor Author

Rayman commented Apr 5, 2024

@shu-beg ros/rosdistro#40476

@Rayman
Copy link
Contributor Author

Rayman commented May 28, 2024

Last sync we caused a regression on the 2.5.1 release for iron. Can we try again next sync? The filter nodes are very useful to have.

@SteveMacenski
Copy link
Member

SteveMacenski commented May 28, 2024

Was that fixed in iron branch? I can run again if we're good to go again.

Sorry, I've had alot on my plate and some things have been intentionally dropped. I'm getting onto the right side of that pile of work this week hopefully :-) Open source maintainers' work is never done, but at some point I as a human need to be done 😆

@Rayman
Copy link
Contributor Author

Rayman commented May 29, 2024

I think we need this PR: #447

So if you cherry pick that commit to iron you should be good to go.

For me personally I would like to see the whole rolling branch released on iron. A lot more code has been ported from ROS1 to ROS2. But I can imagine that would break ABI compatibility

@SteveMacenski
Copy link
Member

ros/rosdistro#41386

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

5 participants