I have a weird thing going on with __DATE__ and __TIME__ when building my app in the yocto environment. I'm building for "genericx86-64" and I'm using __DATE__ and __TIME__ in my source to show what

In addition to the above changes, I also included instructions inside conf/local.conf file to install my first ROS2 package: IMAGE_INSTALL_append=" ros-core my-first-yocto-pkg" After that, I was able

Hello, Matthias. I added `amente-cmake-native` inti DEPENDS and, indeed, I got a different error this time: I needed to append the following lines at the end of my-first-yocto-pkg_git.bb file in

Hi Bojan, I guess this is not the right address. Just saying. You are missing a DEPENDS, ros_ament_cmake does not add it. Try adding ament-cmake-native to your DEPENDS and see if

My solution was to use recipe name without `-native`, and simply use empty packages (no-op) for target. Only nativesdk- and -native variants have an affect. Then add `TOOLCHAIN_HOST_TASK:append = "

Hi all, I'm having some difficulty with setting up users and the respective application user assignments. I have a generic recipe which inherits useradd and sets a user, this works great for my

Actually by removing `inherit native` and adding -native to the recipe name doesn't make it build for native.

To eliminate target option from the recipe I just need to make sure the name of the recipe ends with -native, then removing inherit native works fine.

Hi Jared / all My apologies - I've applied the fix and pushed it to master, thank you! I think it's fair to say this layer is pretty much unmaintained at the moment. I'd be more than happy if

I'm trying to sort out how to install a pre-built host-only tool for native and nativesdk only. Using `inherit native` my-recipe-native and nativesdk-my-recipe both build fine, only -c populate_sdk

I don't see a response yet from Paul Eggleton, how do we proceeded in getting this fixed?

Current Dev Position: YP 3.5 M1 Next Deadline: 6th Dec. 2021 YP 3.5 M1 build Next Team Meetings: Bug Triage meeting Thursday Nov.11th at 7:30am PDT

From: Bartosz Golaszewski <bartosz.golaszewski@...> This adds a recipe for building the lvgl sample from mainline zephyr source. We need to include one upstream patch that fixes a build

From: Bartosz Golaszewski <bartosz.golaszewski@...> As the number of repos pulled gets bigger it's easier to parse them if they are ordered alphabetically. Signed-off-by: Bartosz Golaszewski

From: Bartosz Golaszewski <bartosz.golaszewski@...> This type of multi-line assignments is the most prevalent in well-known layers and is more visually pleasing. Signed-off-by: Bartosz

From: Bartosz Golaszewski <bartosz.golaszewski@...> It's easier to parse visually when those assignments are ordered. Signed-off-by: Bartosz Golaszewski

This series adds a recipe for the lvgl sample from zephyr. Due to how meta-zephyr works we need to pull in some additional modules for the build to succeed. The first three patches are just coding

Following on from Bartosz's recent patch, Naveen suggested I take this to the list. We've been recently discussing some of the drawbacks of meta-zephyr between myself, Diego Sueiro and Jon Mason at

Could you please rebase this series with latest ! Regards, Naveen