[OE-core] Including kernel-devsrc to the SDK while using INCOMPATIBLE_LICENSE

[OE-core] Including kernel-devsrc to the SDK while using INCOMPATIBLE_LICENSE

[Måns]

Hi,

I am trying to add the kernel-devsrc to the SDK by using

TOOLCHAIN_TARGET_TASK_append = "kernel-devsrc"

My problem is that we are trying to prevent GPLv3 packages by setting

INCOMPATIBLE_LICENSE = "GPL-3.0"

This resulting in an issue because the kernel-devsrc depend on GPLv3 packages

RDEPENDS_${PN} = "bc python flex bison ${TCLIBC}-utils"

We are currently using Thud. We are not shipping the SDK so the
INCOMPATIBLE_LICENSE is only needed for the image build. Any
suggestions on the best approach on how to solve this would be really
appreciated.

Thanks

Re: [OE-core] Including kernel-devsrc to the SDK while using INCOMPATIBLE_LICENSE

[Måns]

So for anyone that stumbles across this issue it looks like I was
using the kernel-devsrc in the wrong way.
It seems like it is more for kernel module development done on the
target. I was more interesting in having access to
some kernel driver headers so instead I ended up following

https://docs.yoctoproject.org/singleindex.html#using-headers-to-interface-with-devices

Thanks

Den tis 29 mars 2022 kl 08:52 skrev Måns <mans.zigher@gmail.com>:
>
> Hi,
>
> I am trying to add the kernel-devsrc to the SDK by using
>
> TOOLCHAIN_TARGET_TASK_append = "kernel-devsrc"
>
> My problem is that we are trying to prevent GPLv3 packages by setting
>
> INCOMPATIBLE_LICENSE = "GPL-3.0"
>
> This resulting in an issue because the kernel-devsrc depend on GPLv3 packages
>
> RDEPENDS_${PN} = "bc python flex bison ${TCLIBC}-utils"
>
> We are currently using Thud. We are not shipping the SDK so the
> INCOMPATIBLE_LICENSE is only needed for the image build. Any
> suggestions on the best approach on how to solve this would be really
> appreciated.
>
> Thanks