| Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung |
| software:linux:yocto:workflow [2022-01-13 13:47] – Moritz Lammerich | software:linux:yocto:workflow [2023-05-10 15:03] (aktuell) – Urs Graf |
|---|
| * Each project should have its own layer called ''meta-<projectname>'' to hold any and all changes and additions needed for that project. | * Each project should have its own layer called ''meta-<projectname>'' to hold any and all changes and additions needed for that project. |
| * Each project should also define an image named ''<projectname>-image'' (rather than appending ''ost-image'' et al). | * Each project should also define an image named ''<projectname>-image'' (rather than appending ''ost-image'' et al). |
| * Any changes to recipes other layers (e.g. ''meta-ost'') are carried out by appending the recipe in ''meta-<projectnmae>'' and only upstreamed if deemed appropriate at a later date. | * Any changes to recipes of other layers (e.g. ''meta-ost'') are carried out by appending the recipe in ''meta-<projectname>'' and should only be upstreamed later if deemed appropriate. |
| |
| |
| * ''meta-ost-ros'' | * ''meta-ost-ros'' |
| * ''meta-ost-toradex'' | * ''meta-ost-toradex'' |
| * (''meta-ntb-ethercat'' (internal use only)) | * (''meta-ost-ethercat'' (internal use only)) |
| * ''meta-<projectname>'' | * ''meta-<projectname>'' |
| |
| |
| Recipes and MACHINES that rely on external BSPs should get their own layer named ''meta-ost-<vendor>'', e.g. ''meta-ost-toradex'' for the ''colibri-imx6'' based [[ .:cb20 ]], that requires the Toradex BSP. | Recipes and MACHINES that rely on external BSPs should get their own layer named ''meta-ost-<vendor>'', e.g. ''meta-ost-toradex'' for the ''colibri-imx6'' based [[ .:cb20 ]], that requires the Toradex BSP. |
| This second layer also contains layers such as ''meta-ost-ros'' and ''meta-ntb-ethercat'' which don't rely on external BSPs, but provide optional software features. | This second layer also contains layers such as ''meta-ost-ros'' and ''meta-ost-ethercat'' which don't rely on external BSPs, but provide optional software features. |
| Recipes that require large or numerous dependencies -- such as ''meta-ost-ros'' -- should be split into its own layer as to keep the core build slim. | Recipes that require large or numerous dependencies -- such as ''meta-ost-ros'' -- should be split into its own layer as to keep the core build slim. |
| Lastly, there is the ''meta-<projectname>'' layer. | Lastly, there is the ''meta-<projectname>'' layer. |
| Every project using yocto should have its own layer to hold recipes and changes that are specific to that project. | Every project using yocto should have its own layer to hold recipes and changes that are specific to that project. |
| This strucrture ensures modularity and allows every project to customize the build without changing ''meta-ost'' or its companions. | This structure ensures modularity and allows every project to customize the build without changing ''meta-ost'' or its companions. |
| |
| ===== CI/CD ===== | ===== CI/CD ===== |