Missing dependencies on driver header
I have a niggly problem I keep running into, especially with fresh image builds.
I have a custom driver, and a user-space library for controlling it; therefore the library includes one of the driver's header files (IOCTL defs etc).
However I can't get the dependencies correct in the library recipe so as to get the driver's header installed and available to the library build step. In other words 'bitbake MyDriverLib' gives a "MyDriver.h: no such file or directory "
The lib's recipe includes
inherit autotools lib_package binconfig-disabled pkgconfig
DEPENDS_${PN} = "MyDriver"
RDEPENDS_${PN} = "MyDriver"At 'some point later', the lib *will* build ok: I've done each MyDriver step one by one, and it seems that once the 'install' has been done then MyDriverLib will then compile. ('-c compile MyDriver' isn't sufficient). But shouldn't the RDEPENDS above trigger the MyDriver install?
I'm obviously missing a dependency hook somewhere?
Quoted 4 lines · On Fri, 2017-03-31 at 14:42 +0100, [email protected] wrote:
I have a niggly problem I keep running into, especially with fresh image builds.
I have a custom driver, and a user-space library for controlling it; therefore the library includes one of the driver's header files (IOCTL defs
Quoted 8 lines
etc).
However I can't get the dependencies correct in the library recipe so as to get the driver's header installed and available to the library build step. In other words 'bitbake MyDriverLib' gives a "MyDriver.h: no such file or directory "
The lib's recipe includes
inherit autotoolslib_packagebinconfig-disabled pkgconfig DEPENDS_${PN} = "MyDriver"
Usually I use "DEPENDS" and not "DEPENDS_${PN}".
Else does your kernel module recipe populate sysroot with the header?
Quoted 10 lines
RDEPENDS_${PN} = "MyDriver"
At 'some point later', the lib *will* build ok: I've done each MyDriver step one by one, and it seems that once the 'install' has been done then MyDriverLib will then compile. ('-c compile MyDriver' isn't sufficient). But shouldn't the RDEPENDS above trigger the MyDriver install?
I'm obviously missing a dependency hook somewhere?
Quoted 18 lines · On 31 March 2017 at 14:56 Fabien Lahoudere <[email protected]>…
Quoted 4 lines · On Fri, 2017-03-31 at 14:42 +0100, [email protected] wrote:
I have a niggly problem I keep running into, especially with fresh image builds.
I have a custom driver, and a user-space library for controlling it; therefore the library includes one of the driver's header files (IOCTL defsQuoted 8 lines
etc).
However I can't get the dependencies correct in the library recipe so as to get the driver's header installed and available to the library build step. In other words 'bitbake MyDriverLib' gives a "MyDriver.h: no such file or directory "
The lib's recipe includes
inherit autotoolslib_packagebinconfig-disabled pkgconfig DEPENDS_${PN} = "MyDriver"
Quoted 2 lines
Usually I use "DEPENDS" and not "DEPENDS_${PN}".
Ah, thanks - That seems to have fixed it!
Quoted 16 lines
Else does your kernel module recipe populate sysroot with the header?
Quoted 14 lines
RDEPENDS_${PN} = "MyDriver"
At 'some point later', the lib *will* build ok: I've done each MyDriver step one by one, and it seems that once the 'install' has been done then MyDriverLib will then compile. ('-c compile MyDriver' isn't sufficient). But shouldn't the RDEPENDS above trigger the MyDriver install?
I'm obviously missing a dependency hook somewhere?--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto