зеркало из https://github.com/Azure/meta-iotedge.git
8fb7bf0025
* Add thud support (#19) * Initial thud support * Tweak the recipes and remove invalid items * Make layer thud only * Update README for Thud * Update source mirrors for thud * Update build branch to thud * Add master back * Remove source rev * Update to 1.0.8 (#25) * Update to 1.0.8 * Set libiothsm no build in iotedge-cli * Update to 1.0.9.4 for Thud (#40) * Update to 1.0.9.4 for Thud * Update third party notices md5sum * Pin meta-rust commit version * iotedge-cli RDEPENDS on libiothsm * Add build dependency on libiothsm * Update for dunfell (#43) * Update for dunfell * Use newer version of the rust compiler * RDEPENDS on docker not virtual/docker Remove unused recipes * Disable libgit2 for cargo Without this fix the build leads to an error : "invalid version 3 on git_proxy_options; class=Invalid (3)" * Update Dunfell branch to LTS (1.1.3) (#65) * Add 1.1.3 bitbake files. * Update sums for iotedge project file. * Fix daemon description. * Rmove extraneous comments. * TGZ package structure is a little different. Fix includes in the bitbake file. * Fix license path * Fix install paths. * More clearly mark generated section. * Update README.md (#66) Readme.md: Match the meta-rust layer revision from builds/checkin.yaml * We probably don't need to set CARGO_SRC_DIR (#68) * Update dunfell branch to 1.1.6 (#70) * Update dunfell branch to 1.1.6 * Update Dunfell branch to IoT Edge version 1.1.8 (#73) * Update Dunfell branch to IoT Edge version 1.1.8 * Use a newer container for Yocto builds. Make some script changes due to difference in the containers. * Update the MD5 hash for THIRDPARTYNOTICES. * changed git fetch from nobranch/AUTOREV to main branch (#79) * changed from nobranch/AUTOREV to main branch This fixes a recent bug introduced over the weekend which results in a bitbake expansion error. Specifically the error is the following, Fetcher failure: Unable to resolve 'master' in upstream git repository in git ls-remote output for github.com/Azure/hyperlocal-windows * nobranch/AUTOREV to main branch in iotedge-daemon This fixes a recent bug introduced over the weekend which results in a bitbake expansion error. Specifically the error is the following, Fetcher failure: Unable to resolve 'master' in upstream git repository in git ls-remote output for github.com/Azure/hyperlocal-windows * Update dunfell to 1.1.11 (#82) * Update dunfell to 1.1.11 * Update recipes to 1.1.15 (#85) Update the following recipe components to 1.1.15: - iotedge-cli - iotedge-daemon - libiothsm * Use 1ES agent for Checkin gate (#89) Previously the pipeline was run on the self-hosting pool, the ECSS team has mandate the self-hosting pools need to be retired in favor of the 1ES pools. This PR updates the checkin gate test agent to be running on 1ES VM instead of self-hosting VM. * Yocto Dunfell Recipe for Edge 1.4 (#90) * Draft Recipe for 1.4 IoT Edge * Add Panic strategy to unwind * Update receipes to 1.4.2 * TPM provsioning support and update dependencies * Update recipes to fix bug and Update documentation * Update README.md (#96) * Update Iotedge recipes to 1.4.4 * refactor * Update README.md * 1.4.4 changes * refactor * Update iotedge_1.4.4.bb Co-authored-by: Mike Yagley <myagley@gmail.com> Co-authored-by: David Robson <darobs@microsoft.com> Co-authored-by: František Šindelář <sindelar.fr@gmail.com> Co-authored-by: donofan0 <83614927+donofan0@users.noreply.github.com> Co-authored-by: yophilav <54859653+yophilav@users.noreply.github.com> Co-authored-by: Micah Lewis <1009123+micahl@users.noreply.github.com> |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| builds | ||
| conf | ||
| recipes-core | ||
| recipes-devtools/cargo | ||
| scripts | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
| THIRDPARTYNOTICES | ||
README.md
meta-iotedge
This layer provides support for building IoT Edge with Yocto.
Please see the corresponding sections below for details.
Adding the meta-iotedge layer to your build
Use the branch of meta-iotedge corresponding to your Yocto release:
- Sumo -
git clone -b sumo https://github.com/Azure/meta-iotedge.git - Thud -
git clone -b thud https://github.com/Azure/meta-iotedge.git - Warrior -
git clone -b warrior https://github.com/Azure/meta-iotedge.git - Zeus -
git clone -b zeus https://github.com/Azure/meta-iotedge.git - Dunfell -
git clone -b dunfell https://github.com/Azure/meta-iotedge.git
In almost all cases, you should not use the master branch of meta-iotedge in your image.
Run bitbake-layers add-layer meta-iotedge
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.