diff options
| author | Anatol Belski <anbelski@linux.microsoft.com> | 2021-04-07 11:22:06 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-04-18 11:37:25 +0100 |
| commit | 036a8d4330f27777ce14185c66967ee0b678c0b9 (patch) | |
| tree | f8fb22b3f90e90e9fdeae9706b3499fd9d379c1a /meta/recipes-extended/ltp/ltp_20210121.bb | |
| parent | 0ae3f1edd6c35fe03e810de9eab3a227492084d7 (diff) | |
| download | poky-036a8d4330f27777ce14185c66967ee0b678c0b9.tar.gz | |
cross-canadian: Whitelist "mingw32" as TARGET_OS
If a recipe inherits cross-canadian and contains "nativesdk" in
BBCLASSEXTEND and meta-mingw is included and multiconfig is enabled,
bitbake will generate the correspending recipe. As meta-mingw sets
SDK_OS to "mingw32", that's what TARGET_OS will be set to as well.
Thus, currently such a recipe won't pass the check and fail with
a message:
Building cross-candian for an unknown TARGET_SYS
(x86_64-mysdk-mingw32), please update cross-canadian.bbclass
Even when building an SDK targeting Linux, but the mentioned conditions
are met, bitbake will try to generate the corresponding recipe and fail.
As the described combination seems valid, including "mingw32" into the
whitelist unconditionally as a fix is suggested.
(From OE-Core rev: d9306e8f9dbdbd30382f0bc0f0a1af75e702a2aa)
Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/ltp/ltp_20210121.bb')
0 files changed, 0 insertions, 0 deletions