| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
Two auto-generated recipes don't handle library file extensions correctly and
include *.so files as part of ${PN}:
- liblz4-vendor
- yaml-cpp-vendor
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
|
|
|
|
|
|
| |
Two auto-generated recipes need to have their LICENSE strings fixed:
- sensor-msgs-py
- liblz4-vendor
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The rosbag2/mcap-vendor build was failing due to being unable to
find the requested commit hash.
The originally-generated recipe was mostly correct, but was overridden by a
bbappend, in upstream meta-ros/meta-ros2-jazzy, which replaced the hash with
one from the release/rolling/mcap_vendor/0.24.0-1 branch.
The jazzy branch of meta-ros2 was created from the rolling release branch,
which is why the rosbag2/mcap-vendor recipe had an override which specified
a commit from the rolling branch of rosbag2-release. This wasn't updated to
point to a commit on the jazzy branch when the jazzy branch was created.
Update the SRCREV to point to a release on the release/jazzy/mcap_vendor
branch of rosbag2-release Also, update to the latest commit on this branch.
Additionally the build was failing because it was not able to find necessary
header files that were provided in the source tree.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The rosbag2-compression-zstd build was failing due to a patch failing to apply
to the sources.
Updating the SRCREV to point to the latest commit on the
release/jazzy/rosbag2_compression_zstd branch means the patch is no longer
required, and the build succeeds.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The rosbag2/shared-queues-vendor build was failing due to being unable to find
the requested commit hash from the specified branch (release/jazzy/
shared_queues_vendor/0.26.1-2).
The originally-generated recipe was mostly correct, but was overridden by a
bbappend, in upstream meta-ros/meta-ros2-jazzy, which replaced the hash with
one from the release/rolling/shared_queues_vendor/0.24.0-1 branch.
The jazzy branch of meta-ros2 was created from the rolling release branch,
which is why the rosbag2/shared-queues-vendor recipe had an override which
specified a commit from the rolling branch of rosbag2/shared-queues-vendor.
This wasn't updated to point to a commit on the jazzy branch of
rosbag2/shared-queues-vendor when the jazzy branch was created.
Update the SRCREV to point to a release on the release/jazzy/
shared_queues_vendor branch of rosbag2/shared-queues-vendor Also, update to
the latest commit on this branch.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
The automatically-generated ROS recipes for ros2-jazzy create a liblz4-vendor
recipe (and dependencies) instead of using upstream liblz4. Remove the
liblz4-vendor dependency.
Add a "meta-ros2-jazzy" dynamic layer for ros2-jazzy support.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
