This IoT-Connect connect layer only supports hardknott
The following details yocto layers designed to integrate the IoT-Connect C SDK. The end result is a compiled version of the basic-sample app provided in the C SDK repo that is installed to an image target. Once said image is flashed to a target, the basic-sample app should successfully run & establish comms with an appropriately setup https://avnet.iotconnect.io/
There are 2 layers thus far: meta-iotconnect & meta-myExampleIotconnectLayer.
To include the layers within a yocto enviroment:
-
check them out to the
sourcesdirectory in your yocto enviroment. -
add them to
conf/bblayersfile in your build directory -
add recipes as a part of your image (for example in
<meta-my-layer>/recipes-core/images/<image-name.bb>file) or to your local build configuration (inlocal.conffor example) -IMAGE_INSTALL += " iot-c-sdk" -
build with a bitbake call e.g.
./bitbake <image-name>
Note: you might need adding lines below to your image
inherit core-image
inherit module
inherit extrausers
Contains the git urls for checkouts, recipe definitions & a patch file for temporarily fixing the CMake find_package issue. This layer sets the build target to basic-sample. This might get further subdivided in the future to only provide IoT-Connect libraries to other layers.
It's expected that developers will have to provide bespoke elements for their application. In the basic-sample example you're required to edit app-config.h. This layer provides an example of how a user might specify custom requirements of an application within their layer that's then compiled & built for use: in this case the app-config.h specifics.