You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building a workspace that contains roscopter, I noticed a warning saying
WARNING: Metapackage "roscopter_pkgs" should not have other dependencies besides a buildtool_depend on catkin and exec_depends.
which I now understand to be from some conditional dependencies in roscopter_pkgs/package.xml for ament if the ROS version is ROS 2. Is there still any development towards ROS 2 that is currently happening or any plans of development?
Regardless, I think that anything ROS 2 should go into its own branch and should not be on master, since to my understanding very little porting to ROS 2 has been done. Once a decently stable ROS 2 implementation is working, then we could start merging things over.
That's my opinion. Let me know if there's something I'm missing!
The text was updated successfully, but these errors were encountered:
I had these warnings building a workspace with rosflight_holodeck, but I just now created a test workspace with only roscopter and rosflight (both on master) and I am still getting that warning. It happens during catkin's CMake step.
I should have also mentioned that I'm using ROS noetic on Arch. CMake version is 3.18.
When building a workspace that contains roscopter, I noticed a warning saying
which I now understand to be from some conditional dependencies in
roscopter_pkgs/package.xml
for ament if the ROS version is ROS 2. Is there still any development towards ROS 2 that is currently happening or any plans of development?Regardless, I think that anything ROS 2 should go into its own branch and should not be on
master
, since to my understanding very little porting to ROS 2 has been done. Once a decently stable ROS 2 implementation is working, then we could start merging things over.That's my opinion. Let me know if there's something I'm missing!
The text was updated successfully, but these errors were encountered: