====== Bitbake ======

[[https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-intro.html|BitBake User Manual]]
===== Bitbake tasks =====

  * ''fetch'' If needed, make local copy of remote sources (bz2, git, svn,  ...).
  * ''unpack'' prepare source of package in work directory (bz2 - unpack, git -   clone from local copy, etc)
  * ''patch'' apply all *.patch files from SRC_URI
  * ''configure''
  * ''compile''
  * ''install''
  * ''package'' split installed on fake sysroot files into separate packages:
     * main package or library (package_name)
     * debugging symbols (package_name-dbg)
     * documentation (package_name-doc)
     * locales (package_name-locale)
     * development headers (package_name-dev)

  * ''clean''
  * ''cleanstate'' remove output and SSTATE cache files for given package
          
==== dependency explorer ====

Dependency explorer is replaced by "Task Explorer" in Yocto 3.3.1. [[https://docs.yoctoproject.org/3.3.1/singleindex.html#bitbake-changes|4.10.10 BitBake Changes]]

  * ''bitbake -g -u taskexp''
  * [[http://www.openembedded.org/wiki/Inspect_DEPENDS|Inspect DEPENDS]]
  * [[https://stackoverflow.com/questions/63284156/how-can-i-determine-what-is-causing-an-unwanted-package-to-be-built-in-yocto|How can I determine what is causing an unwanted package to be built in Yocto?]]
  * [[https://stackoverflow.com/questions/67785619/why-is-package-included-in-yocto-rootfs|Why is package included in Yocto rootfs?]]
  * [[https://stackoverflow.com/questions/71121323/yocto-how-to-know-why-a-package-is-included|Yocto: How to know why a package is included?]]