How to build the agent with yocto zeus: about iot-hub-device-update HOT 4 CLOSED

To stay in the spirit of yocto and keep things separated, I added a new target to build against.
You can then place everything that belongs to device update into this target. This has the benefit, that you can still build your base target without having to modify your local.conf.

require recipes-config/images/your-base-image

DESCRIPTION = ""
LICENSE = ""

CORE_IMAGE_EXTRA_INSTALL += " \
    azure-device-update   \
    adu-agent-service \
"

from iot-hub-device-update.

@Voxel07 Thanks for the hint - I only mentioned azure-device-update as dependency in my code, updated now to adu-agent-service which includes the former and adds a daemonized service.

from iot-hub-device-update.

For everyone bumping in here: I created a repository containing a branch for each version of yocto I got the meta-layer running on. Some of them, like the zeus one also contain some useful additions and bugfixes: https://github.com/munit-solutions/meta-azure-device-update/tree/zeus

from iot-hub-device-update.

Hi @SimonSimCity, we currently support honister and have our latest Yocto layers published here: https://github.com/Azure/iot-hub-device-update-yocto

from iot-hub-device-update.