Explanation of yocto project directory structure

General catalogue

The following structure is yocto Some general structures of the project . In practical engineering , Each manufacturer may tailor according to their own needs , But the overall structure and the contents stored in each directory are basically the same .

• bitbake Tool catalog
  bitbake, It's one metedate Interpreter , Read metedate And execute the defined task. perform bitbake On command , In fact, the implementation is bitbake/bin/ The following file .
• build User profile and project build output directory .
  build Directories are created and configuration files are initialized when creating environment variables . All files built are organized and stored in this directory .
• documentation Documentation
• meta OE Core Of Metedata, Include recipes,comon classes etc.
• meta-poky poky Configuration data of the release
• meta-yocto-bsp
  yocto Some references included in the project BSP To configure , Usually, manufacturers will increase their own bsp Catalog .
• meta-selftest OE Self testing recipes and append file
• meta-skeleton BSP and kernel Some temporary for development recipes
• scripts Script files , Functions used to provide some features . This path will be added to the environment variable .
• oe-init-build-env structure OE Environment

build/ The file organization structure under the directory

Be careful ：build Can refer to fsl-release-bsp/imx6ulevk-fb

• build/conf/local.conf
  User profile , Include all customized configurations . All variables configured in this file will override the soft assignment of the corresponding variables in other files （?= form ）（ Be careful = Hard coding of forms cannot cover ）
• build/conf/bblayers.conf
  This file is used to define BBLAYERS,BBLAYERS It is to decide which modules under the path need to be built , What doesn't need to be built , And provide that information to BitBake
• build/conf/sanity_info
  Availability information , No need to pay attention
• build/downloads
  During construction , Download all the source code . You can put this directory under a public directory , Provide compilation efficiency every time
• build/sstate-cache
  Build state cache in build composition . You can put this directory under a public directory , Provide compilation efficiency every time

build/tmp

When building, all the output is stored in this directory

• build/tmp/buildstats
  Build Statistics , Every build , A date directory will be generated under this directory
• build/tmp/cache BitBake analysis metedata( Include recipes and config file ) after , Cache the parsing results in this directory , To improve follow-up efficiency
• build/tmp/deploy Deployment file directory , The final required documents （boot rootfs image etc. ） All in this directory
• build/tmp/deploy/deb Store all generated by the system .deb Installation package of type
• build/tmp/deploy/rpm Store all generated by the system rpm Installation package of type
• build/tmp/deploy/ipk Store all generated by the system ipk Installation package of type
• build/tmp/deploy/licenses License information of various software used by the system
• build/tmp/deploy/images Deposit boot rootfs image Wait for the documents
• build/tmp/deploy/sdk Tool chain installation script
• build/tmp/sstate-control Status tracking file
• build/tmp/sysroots-components Make sysroots Some additional components need to be added before
• build/tmp/sysroots The content of the built root file system
• build/tmp/stamps Record BitBake track task Some information about execution time
• build/tmp/log Log information
• build/tmp/work Include and CPU Working directory related to architecture
• build/tmp/work-shared Work information cache , In order to improve efficiency

meta/ The file organization structure under the directory

• meta/classes All inclusive *.bbclass.class Files are abstract public code , To each package Use .
• meta/conf The configuration file （.conf） Core set of . Like all bblayers The configuration files of are all from this directory bitbake.conf Derived from the document .
• meta/conf/machine machine Configuration file for
• meta/conf/distro Configuration file of release information
• meta/conf/machine-sdk To develop sdk yes 32 A still 64 position .
• meta/files/ Include some licence Some other files needed for file and system construction
• meta/lib/ Some required in the process of system construction Python The library files
• meta/recipes-bsp uboot And other hardware related configuration information
• meta/recipes-connectivity Contains libraries and applications related to communication with other devices
• meta/recipes-core Build basic linux image The dependence needed
• meta/recipes-devtools Required for host construction tools, These tools can also be used on the target board .
• meta/recipes-extended Some unimportant applications
• meta/recipes-gnome GTK+ Framework related applications
• meta/recipes-graphics Drawing related libraries
• meta/recipes-kernel kernel And the libraries that the kernel depends on
• meta/recipes-lsb4 Support Linux Standard Base (LSB) version 4.x The required
• meta/recipes-multimedia Multimedia support , picture 、 voice 、 video
• meta/recipes-rt Support PREEMPT_RT The required recipes And the bag
• meta/recipes-sato/ sato demo
• meta/recipes-support other recipes Some general recipes
• meta/site Cache results under different architectures are stored
• meta/recipes.txt Documentation