spdlog bbappend has wrong version in dunfell branch

[windelbouwman]

Describe the bug

When building ros2 against the openembedded dunfell branch, spdlog_1.8.1.bbappend does not match any recipe. I renamed this to spdlog_1.5.0.bbappend to continue.

To Reproduce

Layers used:

• openembedded-core/meta (dunfell branch)
• meta-openembedded/meta-python (dunfell branch)
• meta-openembedded/meta-oe (dunfell branch)
• meta-ros/meta-ros-common (dunfell branch)
• meta-ros/meta-ros2 (dunfell branch)
• meta-ros/meta-ros2-dashing (dunfell branch)

Command used:

$ bitbake ros2topic

[shr-project]

That's because you're missing meta-ros-backports-gatesgarth layer, see
6afd567
and
880ae22

[windelbouwman]

Ah, okay, I see! Thanks for the tip!

I think it would make sense to add a small howto to the README of this repo how to use it. For example:

Usage

Clone this repository, using the proper branch for your yocto version

$ git clone https://github.com/ros/meta-ros -b dunfell

Add these layers to your bblayers.conf file:

meta-ros/meta-ros-backports-gatesgarth
meta-ros/meta-ros-common
meta-ros/meta-ros2
meta-ros/meta-ros2-dashing

Create an image by your preferred way, for example set IMAGE_INSTALL_append in you local.conf file:

IMAGE_INSTALL_append = " rclpy"

Would it make sense to add this? I was unable to find this usage information so far.

[windelbouwman]

Btw, what does gatesgarth signify?

[shr-project]

Yocto 3.1 release codename is Gatesgarth as mentioned in commit message of the second commit.

For all releases see
https://wiki.yoctoproject.org/wiki/Releases

There is a README file which points to
https://github.com/ros/meta-ros/wiki/OpenEmbedded-Build-Instructions
which describes how to use mcf to get the right set of layers in right revisions (to match exactly what we have tested), if you use different set of layers or different versions then you're bit on your own, but LAYERDEPENDS should guide you about which layers you need, unfortunately this meta-ros-backprots-gatesgarth layer is a bit of exception, because until now we were using identical branch content for dunfell, gatesgarth, hardknott, that will probably change soon and then I'll add meta-ros-backports-gatesgarth to LAYERDEPENDS in dunfell branch as well (and remove the layer completely from gatesgarth and master branches).

[windelbouwman]

I'll add meta-ros-backports-gatesgarth to LAYERDEPENDS in dunfell branch as well (and remove the layer completely from gatesgarth and master branches)

This makes a lot of sense! Thank you for shaping these layers in its current shape!

[windelbouwman]

I am able to build the recipe, but when running ros2 topic list, I get: "Unable to get rmw_implementation_identifier, try specifying the implementation to use via the 'RMW_IMPLEMENTATION' environment variable", and hints on this?

[windelbouwman]

Interesting --> ros2/rcpputils#40

This might be worth a note.

[herb-kuta-lge]

I think it would make sense to add a small howto to the README of this repo how to use it.

Yeah, perhaps the

See here for instructions.

is a little too terse.

[windelbouwman]

Also, I was unable to locate the absolute coolest use-case (in my opinion) of the repo:

1. Inlcude layers in bblayers
2. add package to image
3. profit :)

Benefits of storing the usage in the readme, is that for each branch, there are subtle differences in backports / usage etc.. The wiki might get easy out of sync. The wiki is very useful on it's own, but I'll try to cook up some readme improvements!