971907567c
You need to first set up the build directory by sourcing the poky build script, after that builds can be run in that directory so long as bitbake is in $PATH removing the need to source the init script for each build. i.e: $ . poky-init-build-env ~/my-build $ bitbake some-image <<later, in a different shell>> $ cd ~/my-build $ export PATH=/path/to/bitbake/bin:$PATH $ bitbake an-image This patch also removes use of OEROOT in recipes, etc. Signed-off-by: Joshua Lock <josh@linux.intel.com> |
||
|---|---|---|
| bitbake | ||
| build/conf | ||
| handbook | ||
| meta | ||
| meta-extras | ||
| meta-gnome/packages | ||
| meta-moblin | ||
| meta-openmoko | ||
| scripts | ||
| .gitignore | ||
| LICENSE | ||
| README | ||
| README.hardware | ||
| poky-init-build-env | ||
README
Poky ==== Poky platform builder is a combined cross build system and development environment. It features support for building X11/Matchbox/GTK based filesystem images for various embedded devices and boards. It also supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK with IDE integration. Poky has an extensive handbook, the source of which is contained in the handbook directory. For compiled HTML or pdf versions of this, see the Poky website http://pokylinux.org. Additional information on the specifics of hardware that Poky supports is available in README.hardware.