[OE-core] [PATCH v3] kernel-selftest: Add a recipe on kernel selftest

[Song, Hongzhi]

________________________________________
>From: Richard Purdie [richard.purdie at linuxfoundation.org]
>Sent: Saturday, July 07, 2018 20:14
>To: Song, Hongzhi; openembedded-core at lists.openembedded.org
>Subject: Re: [OE-core] [PATCH v3] kernel-selftest: Add a recipe on kernel selftest

>On Fri, 2018-07-06 at 05:51 -0400, Hongzhi.Song wrote:
>> The recipe builds the framework for kernel-selftest. Now, it just
>> contains two sets of testcase, bpf and vm. We are appending others
>> to the recipe.
>>
>> It needs some features which will be written into relevant recipe.
>> But now, you should add them to conf/local.conf manually.
>> KERNEL_FEATURES_append += "features/bpf/bpf.scc"
>>
>> Signed-off-by: Dengke Du <dengke.du at windriver.com>
>> Signed-off-by: Hongzhi.Song <hongzhi.song at windriver.com>
>> ---
>>  .../kernel-selftest/kernel-selftest.bb             | 94
>> ++++++++++++++++++++++
>>  1 file changed, 94 insertions(+)
>>  create mode 100644 meta/recipes-kernel/kernel-selftest/kernel-
>> selftest.bb
>>
>> diff --git a/meta/recipes-kernel/kernel-selftest/kernel-selftest.bb
>> b/meta/recipes-kernel/kernel-selftest/kernel-selftest.bb
>> new file mode 100644
>> index 0000000..28fd178
>> --- /dev/null
>> +++ b/meta/recipes-kernel/kernel-selftest/kernel-selftest.bb
>> @@ -0,0 +1,94 @@
>> +SUMMARY = "Kernel selftest for Linux"
>> +DESCRIPTION = "Kernel selftest for Linux"
>> +LICENSE = "GPLv2"
>> +
>> +# for bpf and vm
>> +DEPENDS = " \
>> +    elfutils \
>> +    libcap \
>> +    libcap-ng \
>> +    fuse \
>> +    util-linux \
>> +    rsync-native \
>> +"

> This adds a DEPENDS on fuse but fuse is not in OE-Core therefore this
> recipe can never build there.

Considering other kernel-selftest will depend more recipes probably not existing 
in oe-core. So how do you think about that move the recipe to meta-oe.

Best Regards,
-- Hongzhi

> +do_configure[prefuncs] += "copy_perf_source_from_kernel remove_clang_related"
> +python copy_perf_source_from_kernel() {

> We're copying to perf source here? The function name needs tweaking.

> Cheers,

> Richard