Thanks Tim for the link, I have built the iwd. According to Daniel's advice to configure with "--disable-wifi, --enable-iwd", I added PACKAGECONFIG[wifi] = "--disable-wifi, --enable-iwd", to override

I forgot to include the recipe link: https://layers.openembedded.org/layerindex/recipe/89268/

Please look at the layer index for recipes: https://layers.openembedded.org/layerindex/branch/master/layers/ I don’t have any advice for building it however.

Does the following help? https://github.com/mendersoftware/meta-mender-community/tree/dunfell/meta-mender-rockchip

merged.

Hi, Given the high profile of iwd and advocating connman with iwd, I believe someone have already built Yocto connman and iwd, surprisingly, I could not even find an iwd recipe

Hi, Please correct me, but it seems to me the connman is moving to a direction to ditch out wpa_supplicant and to use iwd, but the Honister still configure connman with wpa_supplicant by default,

Hi guys, I have an issue related to vardeps where I am making a task dependent on some variables. I have created some new variables e.g., NEW_VARIABLE, added them to BB_ENV_EXTRAWHITE. In some

Thanks! A few repositories became uncategorized, and clutter the page at the top: https://git.yoctoproject.org/ Alex

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alexandre, Bruce, Michael, Stephen, Randy, Richard, Tim, Trevor ARs: N/A Notes:

Publish the generic-arm64 binaries in a dedicated meta-arm/ directory so it is clear this isn't from the core layers. Signed-off-by: Ross Burton <ross.burton@...> --- scripts/publish-artefacts |

There's a section about building from source with a patch in the article he linked with his first message. I don't know much about python in yocto, but maybe doing that in a recipe could work?

Thanks for the reply, I tried adding IMAGE_LINGUAS = " ", it passes but do_image_cpio gives nothing (means no image.gpio.gz) is generated. I don't know why.

You could define a new uninative_changeinterp() function in your recipe to override the core one and make it do nothing. Not a particularly elegant solution but should work... Cheers, Richard

I agree with Quentin here. Until we have a better mechanism (to rebuild only modified branches not all of them each time, ..) I think we should continue to build them all.

Hi, I need to add TI MCU firmware as part of an OE/Yocto build for a project that I am working on. Basically, the firmware needs to be built during the overall image build and be stored in the RFS.

The migration is complete. git.yoctoproject.org now serves from a pair of load balanced mirrors. push.yoctoproject.org is on a new dedicated secure host. If git push hangs please double check the git

Instead of having a limited set of builders which can deploy artefacts, let every builder have the ability to deploy. This makes it easier to experiment with deploy steps. Signed-off-by: Ross Burton

Signed-off-by: Michael Opdenacker <michael.opdenacker@...> --- scripts/run-docs-build | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/scripts/run-docs-build

Hi Quentin, Thanks for casting your vote. It makes sense. I'll send another patch with this decision in the comments. Cheers Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel