ros-acceleration / ros2acceleration Goto Github PK

In Install page point 5
5. build the workspace and deploy firmware for hardware acceleration

**colcon build --merge-install** is failing with below error

[Processing: acceleration_firmware_kv260]
[Processing: acceleration_firmware_kv260]
[Processing: acceleration_firmware_kv260]
--- stderr: acceleration_firmware_kv260
chmod: cannot access '/scratch/krs_ws/install/../acceleration/firmware/kv260/imagebuilder/scripts': No such file or directory
---
Finished <<< acceleration_firmware_kv260 [2min 4s]

Summary: 13 packages finished [2min 5s]
  1 package had stderr output: acceleration_firmware_kv260

[STATUS: RELEASED - LIVE ON JAMMY]

Buildfarm Status

• dev (ubuntu_jammy_amd64)
• doc (ubuntu_jammy_amd64)
• src (rhel_8)
• src (ubuntu_jammy)
• bin (ubuntu_jammy_amd64)
• bin (rhel_8_x86_64)
• bin (ubuntu_jammy_arm64)

Description

This issue tracks the status for the release of this repository into rosdistro and making it available for installation as .deb via the ROS 2 repositories.

It will detail the steps that need to be taken, and what recommended changes are good to have.

Highlights

• There seem to be extraneous dependencies
• Remember to create a new release tag to reflect the change.

Release Process

Steps

• Remove extra dependencies (e.g. geometry_msgs doesn't seem to be used)
  .
• Create a new release tag corresponding to the version specified in package.xml @vmayoral
• Create release repo (pending ros2-gbp/ros2-gbp-github-org#22)
• Add humble and rolling branches
• Do bloom release
  • bloom should PR rosdistro, if not, manually create a PR
  • ros/rosdistro#32594
• Set appropriate permissions for PR testing
• rosdistro team to review package and merge PR (1-2 days, 1 month to get apt installable)
• Monitor build and release status on repo page and buildfarm

Recommendations

• It'll be good if you can get the linters to run cleanly
• README.md with usage examples