diff options
author | Juro Bystricky <juro.bystricky@intel.com> | 2017-01-15 11:13:36 -0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-03-16 15:34:08 +0000 |
commit | ca66b08b3b7254dea23d1a8ac9eedbe2396e7f12 (patch) | |
tree | f3fd6f3c66cbcd7540b55f96e8e1045d1d0e460f /bitbake/lib/bb/cache.py | |
parent | c8daf507295b76c0ea080e043a6e7a26dcdd83e4 (diff) | |
download | poky-ca66b08b3b7254dea23d1a8ac9eedbe2396e7f12.tar.gz |
bitbake: cooker.py: new multiconfig '*' syntax support
Currently you cannot build a target for all the configured multiconfigs without
specifying a list. The list can be quite long, requiring to type several lines
of text.
This enhancement is to support globbing so that you can do this,
e.g. instead of:
$ bitbake multiconfig:A:bash multiconfig:B:bash bash
you can do:
$ bitbake multiconfig:*:bash
There are real world use cases where it is desirable to use multiconfig with
two different tasks. For example: SDKs with multiple toolchains but also
containing set of additional host tools, or multiconfig builds requiring one image for
the main CPU(s) and a different co-image for a companion CPU.
For this reason, two variations of the new syntax are supported.
For example, the following:
$ bitbake multiconfig:*:meta-toolhchain
would expand to:
$ bitbake multiconfig:A:meta-toolchain multiconfig:B:meta-toolchain meta-toolchain
However the following:
$ bitbake multiconfig:*:meta-toolhchain hosttools
would expand to:
$ bitbake multiconfig:A:meta-toolchain multiconfig:B:meta-toolchain hosttools
In other words, if the user specified the "default" task explicitly, it replaces the implicit
"default" task.
[YOCTO#10680]
(Bitbake rev: 3e80d47bea51b64ed6c8bffc033f2d11a630481e)
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/cache.py')
0 files changed, 0 insertions, 0 deletions