[yocto] Formulating Recipe for out-of-tree kernel module

[Chris Trobridge]

At the risk of answering my own question...
Splitting a driver package into a module recipe and a separate recipe for user-mode utilities works in that each recipe uses the appropriate build process and puts files in the appropriate subdirectory of /work/.
I still don't see a way to build one out-of-tree module against another.  I am interested in opinion on this.  Should I try to get these drivers built in tree?  They seem to be the only two out-of-tree drivers in the build at present.  There is also some facility to add extra modules to the dahdi linux build, although achieving this with bitbake could be challenging too.

Cheers,Chris

From: christrobridge at hotmail.com
To: yocto at yoctoproject.org
Date: Mon, 9 May 2016 12:15:26 +0100
Subject: [yocto] Formulating Recipe for out-of-tree kernel module




I am looking to produce a recipe for the amfeltec usb-fxs adaptor (http://amfeltec.com/products/piranha-usb-fxs-adapter/), with the intention of contributing this to the meta-telephony layer.
However, I have found a few obstacles to getting a clean recipe:The makefile produces both a kernel module and a user utility, with the latter being hard-coded to build with g++.  I can produce a recipe to produce one or other of the components but not both.  Given the structure of the build directories, should this be be achievable, or should I be spitting up the recipe in two?Dahdi header files and Modules.symvers are required.  A header file is used to deduce the version of Dahdi, Modules.symvers is required for the module build process.  Hence, requires the location of the Dahdi source/build directory.  This can be set relative to the amfeltec work directory but this feels wrong.
In more general terms my questions are:Should I split a recipe into kernel and non-kernel components?How should one out-of-tree recipe access the headers/Module.symvers from another (should that recipe be installing them in ${STAGING_KERNEL_DIR} (or somewhere else)?)
Cheers,Chris
 		 	   		  

-- 
_______________________________________________
yocto mailing list
yocto at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160510/385c804d/attachment.html>