Hello! I'm totally new to yocto and mainly new to linux development as a whole. Thus, please excuse me if my concerns that I raise here are inadequate.
== Context == We are developing a quite simple kernel driver that will make use of the GPIO. For a better reproducibility of the development infrastructure, we would like to be able to build this module against an SDK that is provided by the yocto build. == Setup == While the yocto documentation provides a way to build the kernel module during the yocto build, according to this documentation: https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#incorporating-out-of-tree-modules ( https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#incorporating-out-of-tree-modules, ) , we were thinking to make use of the SDK to decouple the development phase of the module from the yocto build. In order to achieve this, the SDK requires the kernel to be configured according to the machine configuration. We expected to be able to have yocto export in the SDK the kernel headers already compiled according to the target environment. However, we couldn't achieve this objective (maybe we're missing something!!). The farthest we could go is to have yocto export the kernel sources into the SDK (according to this SO post https://stackoverflow.com/a/31261404/676344 ), but then, configuring it was not documented. == Conclusion == We would like to know what is the best practice, from a development and continuous integration perspective, to be able to develop a kernel module. Your advice is highly appreciated. Thank you, Alexandru
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49427): https://lists.yoctoproject.org/g/yocto/message/49427 Mute This Topic: https://lists.yoctoproject.org/mt/74249707/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
