Poky tree structure.

yulin@WNC:/work/yulin/ais9628/apps_proc$ find poky/ -type d | grep 'arch/arm/include/generated/uapi/asm'
poky/build/tmp-glibc/work/cortexa8hf-vfp-neon-oe-linux-gnueabi/linux-libc-headers/4.1-r0/linux-4.1/arch/arm/include/generated/uapi/asm
poky/build/tmp-glibc/work/mdm9607_hf-oe-linux-gnueabi/linux-quic/git-r5_perf/build/arch/arm/include/generated/uapi/asm
=== poky/build/tmp-glibc/work-shared/mdm9607-hf/kernel-build-artifacts/arch/arm/include/generated/uapi/asm

poky/build/tmp-glibc/work/mdm9607_hf-oe-linux-gnueabi/linux-quic/git-r5_perf/build/sound/soc/codecs/tlv320aic3x.o

apps_proc/kernel/msm-3.18
=== apps_proc/poky/build/tmp-glibc/work-shared/mdm9607-hf/kernel-source
--> apps_proc/poky/build/tmp-glibc/work/mdm9607_hf-oe-linux-gnueabi/linux-quic/git-r5_perf/build/
drwxr-xr-x  3 yulin yulin      4096 Aug 30 10:55 arch
drwxr-xr-x  3 yulin yulin      4096 Aug 30 10:57 block
drwxr-xr-x  2 yulin yulin      4096 Aug 30 10:57 crypto
drwxr-xr-x 61 yulin yulin      4096 Aug 30 10:57 drivers
drwxr-xr-x 36 yulin yulin      4096 Aug 30 10:57 firmware
drwxr-xr-x 16 yulin yulin      4096 Aug 30 10:56 fs
drwxr-xr-x  4 yulin yulin      4096 Aug 30 10:55 include
drwxr-xr-x  2 yulin yulin      4096 Aug 30 10:57 init
drwxr-xr-x  2 yulin yulin      4096 Aug 30 10:55 ipc
drwxr-xr-x 12 yulin yulin      4096 Aug 30 10:56 kernel
drwxr-xr-x  5 yulin yulin     12288 Aug 30 10:56 lib
-rw-r--r--  1 yulin yulin       735 Aug 30 10:57 Makefile
drwxr-xr-x  2 yulin yulin      4096 Aug 30 10:56 mm
-rw-r--r--  1 yulin yulin     12690 Aug 30 10:55 modules.builtin
-rw-r--r--  1 yulin yulin       547 Aug 30 10:57 modules.order
-rw-r--r--  1 yulin yulin    395649 Aug 30 10:57 Module.symvers
drwxr-xr-x 23 yulin yulin      4096 Aug 30 10:56 net
drwxr-xr-x  6 yulin yulin      4096 Aug 30 10:55 scripts
drwxr-xr-x  3 yulin yulin      4096 Aug 30 10:55 security
drwxr-xr-x 20 yulin yulin      4096 Aug 30 10:56 sound
lrwxrwxrwx  1 yulin yulin        87 Aug 30 10:57 source -> /work/yulin/ais9628/apps_proc/poky/build/tmp-glibc/work-shared/mdm9607-hf/kernel-source
-rw-r--r--  1 yulin yulin   2330247 Aug 30 10:57 System.map
drwxr-xr-x  2 yulin yulin      4096 Aug 30 10:55 usr
-rwxr-xr-x  1 yulin yulin 115048820 Aug 30 10:57 vmlinux
-rw-r--r--  1 yulin yulin 203867180 Aug 30 10:57 vmlinux.o

==> apps_proc/poky/build/tmp-glibc/work-shared/mdm9607-hf/kernel-build-artifacts/
drwxr-xr-x 3 yulin yulin    4096 Aug 30 10:57 arch
drwxr-xr-x 4 yulin yulin    4096 Aug 30 10:57 include
-rw-r--r-- 1 yulin yulin       8 Aug 30 10:57 kernel-abiversion
-rw-r--r-- 1 yulin yulin     735 Aug 30 10:57 Makefile
-rw-r--r-- 1 yulin yulin  395649 Aug 30 10:57 Module.symvers
drwxr-xr-x 6 yulin yulin    4096 Aug 30 10:57 scripts
-rw-r--r-- 1 yulin yulin 2330247 Aug 30 10:57 System.map-3.18.48
drwxr-xr-x 3 yulin yulin    4096 Aug 30 10:57 usr

Linux compilation guide

# Clean, fetch, configure, and compile in poky/yocto
rebake virtual/kernel
or
bitbake -fc virtual/kernel

# Failure : .. is not clean, please run 'make mrproper'
# Failure : .config is missing.  Please run 'make oldconfig', or 'make menuconfig'
! Checking Makefile you can see this error occurs when .config is missing or include/config/ exists.
ls -l include/config/                     #very likely empty
rm -fr include/config/


# Build Linux kernel only for Android

(rm -fr out/..../kernel/...)
make -j bootimage

[BUILD] iperf

## Build iperf-2.0.5 for MDM9607 LE 2.0.1 r00075

cd /work/yulin
git clone git://git.openembedded.org/meta-openembedded
cd meta-openembedded
git checkout -b iperf2 8a0667b25dfd25cae4ac200dcfb63d123858ad57

cd /work/yulin/ais9628/apps_proc/poky/meta-qti-bsp/recipes-extended/
rm -fr iperf
cp -pR /work/yulin/meta-openembedded/meta-oe/recipes-benchmark/iperf .

cd /work/yulin/ais9628/apps_proc/poky/
. build/conf/set_bb_env.sh
export MACHINE=mdm9607
export DISTRO=mdm-perf
bitbake iperf

---> tmp-glibc/work/armv7a-vfp-neon-oe-linux-gnueabi/iperf/2.0.5-r0/package/usr/bin/iperf

Poky vs Yocto vs OpenEmbedded

Package list: apps_proc/oe-core/build/tmp-glibc/deploy/images/<target>/<image>.rootfs.manifest

1. Why not just call this project Poky? What has changed between Poky and the Yocto Project?

The Yocto Project is an umbrella project. Accordingly, it includes a number of projects and resources specifically intended for facilitating development with Linux on embedded devices, and it is an appropriate place for larger organizations to collaborate on the development of build infrastructure for embedded Linux. Poky is one of the the largest components of the Yocto Project, and Poky continues as an independent, open source project developing the build system used by the Yocto Project, as well as by other open source projects.

Poky is a reference system for the Yocto Project, showing how the tools work together. It includes BitBake, openembedded-core, and several other components that anyone can use to start developing with embedded Linux. Poky as a build system is tested by the Yocto Project teams before each release. When you download and use the Yocto Project build system, you are actually downloading Poky and using it to create a distribution that by default is also named Poky. (You can, of course, name your distribution anything you like.)


2. What is the difference between OpenEmbedded and the Yocto Project?

The Yocto Project and OpenEmbedded share a core collection of metadata called openembedded-core. However, the two organizations remain separate, each with its own focus. OpenEmbedded provides a comprehensive set of metadata for a wide variety of architectures, features, and applications. The Yocto Project focuses on providing powerful, easy-to-use, interoperable, well-tested tools, metadata, and board support packages (BSPs) for a core set of architectures and specific boards.