From: <colin.helliwell@ln-systems.com>
To: "'Daniel.'" <danielhilst@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Making header of out-of-tree module available
Date: Mon, 30 Jan 2017 17:05:48 -0000 [thread overview]
Message-ID: <009501d27b1b$1ab18260$50148720$@ln-systems.com> (raw)
In-Reply-To: <CAF3SDA6e7s6kei9+oYSMsG01JnsrA-HrOWUBFOuEE-crLRSHMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2337 bytes --]
Thanks Daniel,
I’ve given that a try, but the header isn’t appearing (with ‘bitbake rfctrl’) anywhere but the module’s own workdir.
It’s recipe is
SUMMARY = " RF driver"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e"
inherit module
SRC_URI = "file://Makefile \
file://rfctrl.c \
file://rfctrl.h \
file://COPYING \
"
FILES_${PN}-dev = "/usr/include/rfctrl/linux/rfctrl.h"
S = "${WORKDIR}"
With a makefile:
obj-m := rfctrl.o
SRC := $(shell pwd)
all:
$(MAKE) -C $(KERNEL_SRC) M=$(SRC)
modules_install:
$(MAKE) -C $(KERNEL_SRC) M=$(SRC) modules_install
clean:
rm -f *.o *~ core .depend .*.cmd *.ko *.mod.c
rm -f Module.markers Module.symvers modules.order
rm -rf .tmp_versions Modules.symvers
From: Daniel. [mailto:danielhilst@gmail.com]
Sent: 30 January 2017 16:46
To: colin.helliwell@ln-systems.com
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Making header of out-of-tree module available
You don't, you make your library depends on your driver, and not on kernel exported headers. In my case I add the header to the -dev package and make the library compilation depend on kernel module.
# kernel-module-foo.bb <http://kernel-module-foo.bb>
FILES_${PN}-dev = "/usr/include/foo/linux/foo.h"
# libfoo.bb <http://libfoo.bb>
DEPENDS = "kernel-module-foo"
Cheers
2017-01-30 13:37 GMT-02:00 <colin.helliwell@ln-systems.com <mailto:colin.helliwell@ln-systems.com> >:
I have a recipe which builds my own (out-of-tree) driver module – this packages/installs the module fine. (It’s recipe has “inherit module”).
Now I’m writing a recipe to build a library which uses the driver. What’s needed to get the driver’s header file ‘exported’ so that it can be included by the library’s recipe?
Thanks
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto
--
"Do or do not. There is no try"
Yoda Master
[-- Attachment #2: Type: text/html, Size: 11453 bytes --]
next prev parent reply other threads:[~2017-01-30 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 15:37 Making header of out-of-tree module available colin.helliwell
2017-01-30 16:46 ` Daniel.
2017-01-30 17:05 ` colin.helliwell [this message]
2017-01-30 17:13 ` Daniel.
2017-01-30 17:14 ` Daniel.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='009501d27b1b$1ab18260$50148720$@ln-systems.com' \
--to=colin.helliwell@ln-systems.com \
--cc=danielhilst@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.