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>
LAYERDIR is one of the few variables which requires immediate expansion and is
worth documenting explicitly.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Collections and overlays are deprecated in favour of layers, a much cleaner and
non-intrusive way of extending Poky with custom recipes, classes and
configuration.
This patch updates the Extending Poky section of the handbook to show how to
use layers to tailor Poky while dropping the existing section on using
collections.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Add more details on using in a team environment and how collections
can be used to manage groups of different kinds of changes
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Joshua Lock
Nitin A Kamble
Richard Purdie
Richard Purdie
Andrzej Zaborowski
Robert Bragg
Richard Purdie