Download meta.bbclass - Yocto Project

Source Directory Structure
Once the build process gets the sample file, it uses sed to substitute final ${OEROOT} values for all
##OEROOT## values.
Note
You
can
see
how
the
TEMPLATECONF
variable
scripts/oe-setup-builddir
script in the Source Directory [http://www.yoctoproject.org/docs/1.6.1/dev-manual/devmanual.html#source-directory]. You can find the Yocto Project version of the
bblayers.conf.sample file in the meta-yocto/conf directory.
6.2.4. build/conf/sanity_info
This file indicates the state of the sanity checks and is created during the build.
6.2.5. build/downloads/
This directory contains downloaded upstream source tarballs. You can reuse the directory for multiple
builds or move the directory to another location. You can control the location of this directory through
the DL_DIR variable.
6.2.6. build/sstate-cache/
This directory contains the shared state cache. You can reuse the directory for multiple builds or
move the directory to another location. You can control the location of this directory through the
SSTATE_DIR variable.
6.2.7. build/tmp/
The OpenEmbedded build system creates and uses this directory for all the build system's output.
The TMPDIR variable points to this directory.
BitBake creates this directory if it does not exist. As a last resort, to clean up a build and start it
from scratch (other than the downloads), you can remove everything in the tmp directory or get rid
of the directory completely. If you do, you should also completely remove the build/sstate-cache
directory.
6.2.8. build/tmp/buildstats/
This directory stores the build statistics.
6.2.9. build/tmp/cache/
When BitBake parses the metadata, it creates a cache file of the result that can be used when
subsequently running commands. BitBake stores these results here on a per-machine basis.
6.2.10. build/tmp/deploy/
This directory contains any "end result" output from the OpenEmbedded build process. The
DEPLOY_DIR variable points to this directory. For more detail on the contents of the deploy directory,
see the "Images" and "Application Development SDK" sections.
6.2.11. build/tmp/deploy/deb/
This directory receives any .deb packages produced by the build process. The packages are sorted
into feeds for different architecture types.
6.2.12. build/tmp/deploy/rpm/
This directory receives any .rpm packages produced by the build process. The packages are sorted
into feeds for different architecture types.
69