Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
software:linux:yocto:workflow [2023-05-10 15:01] Urs Grafsoftware:linux:yocto:workflow [2023-05-10 15:03] (aktuell) Urs Graf
Zeile 19: Zeile 19:
  
 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 =====