Infoportal
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
| software:linux:yocto:devtool [2021-11-29 11:08] – Marco Fuchs | software:linux:yocto:devtool [2023-11-16 15:23] (aktuell) – Urs Graf | ||
|---|---|---|---|
| Zeile 2: | Zeile 2: | ||
| '' | '' | ||
| - | It is available as part of the yocto build environment either through setting up a [[ setup | full yocto build environment ]] or through the [[ sdk | extensible | + | It is available as part of the yocto build environment either through setting up a full yocto build environment, see [[ setup | Setup and Building |
| - | Upon invoking | + | Invoking |
| - | The workspace also includes the sources for all recipes touched by '' | + | The workspace also includes the sources for all recipes touched by '' |
| Furthermore, | Furthermore, | ||
| Zeile 12: | Zeile 12: | ||
| ==== devtool add ==== | ==== devtool add ==== | ||
| + | You can add your own sources and automatically create recipes as given in [[https:// | ||
| + | <code text> | ||
| + | devtool add < | ||
| + | </ | ||
| ==== devtool modify ==== | ==== devtool modify ==== | ||
| Zeile 21: | Zeile 25: | ||
| ==== devtool reset ==== | ==== devtool reset ==== | ||
| - | Use the '' | + | Use the '' |
| + | |||
| + | <code text> | ||
| + | devtool reset < | ||
| + | </ | ||
| ==== devtool menuconfig ==== | ==== devtool menuconfig ==== | ||
| + | Use the '' | ||
| + | <code text> | ||
| + | devtool menuconfig < | ||
| + | </ | ||
| ==== devtool | ==== devtool | ||
| + | Allow to complete the development done through devtool by updating layer(s) with the work done. Pushes any committed changes to the specified recipe to the specified layer and removes it from your workspace. | ||
| + | <code text> | ||
| + | devtool finish < | ||
| + | </ | ||
| ==== devtool build-image ==== | ==== devtool build-image ==== | ||
| Zeile 33: | Zeile 49: | ||
| devtool build-image < | devtool build-image < | ||
| </ | </ | ||
| + | The output tells in which directory the new image was created. | ||
| + | ==== devtool build ==== | ||
| + | If the change affects only one or a few recipes, you can build this recipes individually with: | ||
| + | <code text> | ||
| + | devtool build < | ||
| + | # for example: | ||
| + | devtool build ethercattest | ||
| + | </ | ||
| + | ==== devtool deploy-target ==== | ||
| + | The recipe changes described above can be deployed directly to the target machine using the following command: | ||
| + | |||
| + | <code text> | ||
| + | devtool deploy-target < | ||
| + | |||
| + | # for example: | ||
| + | devtool deploy-target ethercattest root@146.136.37.133 | ||
| + | </ | ||
| + | |||
| + | ===== Use Cases ===== | ||
| + | - Modify the device tree of the kernel and put the changes into its own layer <code text> | ||
| + | # build image for [[software: | ||
| + | # alter device tree in build/ | ||
| + | # commit changes | ||
| + | $ bitbake-layers create-layer ../ | ||
| + | $ bitbake-layers add-layer ../ | ||
| + | $ devtool finish -f linux-stable-rcn-ee ../ | ||
| + | </ | ||
| + | - Repository of used library has new commit. How can you force yocto to fetch the new commit and rebuild the image? Simply, change the source reference in the recipe, e.g. <code text> | ||
| + | #SRCREV = " | ||
| + | SRCREV = " | ||
| + | </ | ||