When packages are built, they are placed inside the working directory of your project, usually tmp/work, and classified according to their architecture. For example, on a wandboard build, we find the following directories:

• all-poky-linux: This is used for architecture-independent packages
• cortexa9hf-neon-poky-linux-gnueabi: This is used for cortexa9, hard floating point packages
• cortexa9hf-neon-mx6qdl-poky-linux-gnueabi: This is used for cortexa9, hard floating point packages that are specific to the i.MX6 architecture
• wandboard-poky-linux-gnueabi: This is used for machine-specific packages, in this case wandboard
• x86_64-linux: This is used for the packages that form the host sysroot
• x86_64-nativesdk-pokysdk-linux: This is used for host packages that are to be included in the SDK, for example, development tools that are built by Yocto but are to be used in the native host

BitBake will build all the packages included in its dependency list inside its own directory.