-
Notifications
You must be signed in to change notification settings - Fork 51
Open
Description
${ROS_DEMO_PACKAGES} \ |
See above. This is duplicatively pulling in demos, not ros2-control. Nominally, this would be the fix:
diff --git a/recipes-core/packagegroups/packagegroup-petalinux-ros.bb b/recipes-core/packagegroups/packagegroup-petalinux-ros.bb
index c97813d..b6b15bf 100644
--- a/recipes-core/packagegroups/packagegroup-petalinux-ros.bb
+++ b/recipes-core/packagegroups/packagegroup-petalinux-ros.bb
@@ -148,7 +148,7 @@ RDEPENDS:${PN}-demo:aarch64 = "\
"
RDEPENDS:${PN}-control:aarch64 = "\
- ${ROS_DEMO_PACKAGES} \
+ ${ROS_CONTROL_PACKAGES} \
"
RDEPENDS:${PN}-dev:aarch64 = "\
However, if one is to actually attempt to build the ROS_CONTROL_PACKAGES
recipes, the build will fail. Those recipes are these:
SUMMARY:${PN}-control = "ROS_CONTROL_PACKAGES includes ROS control packages"
ROS_CONTROL_PACKAGES = "\
controller-interface \
controller-manager \
controller-manager-msgs \
hardware-interface \
ros2-control \
ros2controlcli \
ros2-control-test-assets \
transmission-interface \
"
When I check what content is included for meta-ros from petalinux 2022.2, it is very close to this: https://github.com/ros/meta-ros/tree/honister
So I think the problem is two-fold:
- packagegroup-petalinux-ros purports to pull in ros2-control, but doesn't actually do so; hence there is no CI coverage or visibility into those recipes failing
- AND those recipes do fail to build, as they seem to be broken in meta-ros:honister.
Metadata
Metadata
Assignees
Labels
No labels