Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
software:linux:yocto:kernel [2020-05-27 11:20] mlammerichsoftware:linux:yocto:kernel [2020-05-27 11:28] (aktuell) mlammerich
Zeile 64: Zeile 64:
 ^ command ^ description | ^ command ^ description |
 | bitbake virtual/kernel -c unpack | unpack kernel | | bitbake virtual/kernel -c unpack | unpack kernel |
-| bitbake virtual/kernel -c patch | patch kernel |+| bitbake virtual/kernel -c patch | apply patches (if any) |
 | bitbake virtual/kernel -c compile | build kernel | | bitbake virtual/kernel -c compile | build kernel |
 +| bitbake virtual/kernel -c configure | configure kernel* |
 | bitbake virtual/kernel -c menuconfig | menuconfig, like ''make menuconfig'' | | bitbake virtual/kernel -c menuconfig | menuconfig, like ''make menuconfig'' |
 | bitbake virtual/kernel -c clean | clean kernel package, like ''make clean'' | | bitbake virtual/kernel -c clean | clean kernel package, like ''make clean'' |
 | bitbake virtual/kernel | build and install kernel package | | bitbake virtual/kernel | build and install kernel package |
 +
 +*: ''configure'' also extracts the kernel into ''tmp/work-shared/<machine>/kernel-source''.
 +This is convenient when needing to modify the kernel, for example to create patches.
  
 Note that bitbake will also run all commands that need to be run to execute the specified command. Note that bitbake will also run all commands that need to be run to execute the specified command.
 For example, ''compile'' will also cause ''unpack'' and ''patch'' to be run, since these need to happen before the build. For example, ''compile'' will also cause ''unpack'' and ''patch'' to be run, since these need to happen before the build.