diff options
| author | Awais Belal <awais_belal@mentor.com> | 2018-09-05 22:26:41 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-09-10 12:15:04 +0100 |
| commit | c1f5ec8f4310fb4a53aca34c841b7353fdfb8e28 (patch) | |
| tree | 23236ecd86f859913736bb1c6a0d33d775c51f0f /bitbake/lib/bb/__init__.py | |
| parent | e44bb5b5c8c20af0a87f9c2498c391f764195c32 (diff) | |
| download | poky-c1f5ec8f4310fb4a53aca34c841b7353fdfb8e28.tar.gz | |
bitbake: toaster: use a more flexible way to find bitbake
The current mechanism for finding the bitbake binary
assumes a directory structure which is identical to
poky, where oe-core's meta and bitbake directories are
at the same level. There can be a case where bitbake
is used from elsewhere and in such cases the above
mentioned assumption fails to hold, whereas this is
totally allowed by the oe-init-build-env script which
can take bitbakedir as an argument.
The better approach is to allow bitbake to be derived
from PATH, while keeping the older mechanism in place so
it can be removed after tests are done in various
environments. This makes more sense as toaster has
also been launched from the same bitbake instance
that is the one in PATH.
[YOCTO #12891]
(Bitbake rev: 15340edce23e63b060c75114d508e1f76757239c)
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: David Reyna <David.Reyna@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/__init__.py')
0 files changed, 0 insertions, 0 deletions