diff options
author | Ross Burton <ross.burton@arm.com> | 2025-06-05 21:11:51 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-06-09 17:43:41 +0100 |
commit | 8644f202a141f70e6c4bcbcd9dd3e2fd017cde0a (patch) | |
tree | 185b79ec19b6f6bc85c357c60a6c2a8c0b7b3ad1 /meta/lib/patchtest/patchtest_parser.py | |
parent | dfb58eeeab676b196c273ab6e4041e94cee10d1d (diff) | |
download | poky-8644f202a141f70e6c4bcbcd9dd3e2fd017cde0a.tar.gz |
insane: add test for recipe naming/class mismatches
It's not unheard of for new users to create a recipe called foo-native
that has BBCLASSEXTEND="native" instead of "inherit native". This will
result in a foo-native recipe that is actually a target recipe, and a
foo-native-native recipe for native builds.
Add a test in recipe_qa to verify that recipes called -native inherit
native, and recipes called nativesdk- inherit nativesdk.
As this behaviour is expected, add the new test to the set of tests
required to pass for Yocto Project Compatible status.
(From OE-Core rev: ec2c10a3e85d0772135289fe416d13fa3afca571)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/patchtest/patchtest_parser.py')
0 files changed, 0 insertions, 0 deletions