On Tue, Jul 10, 2018 at 12:11 AM, Michael Allwright
wrote:
> Am I correct in expecting that, if I do everything correctly, my header file
> from module-a should end up in
> ~/poky/build/tmp/work-shared/machine/kernel-source/include/linux/mfd
No, the kernel-source directory is for the kernel
On Tue., 10 Jul. 2018, 00:15 Andre McCurdy, wrote:
> On Mon, Jul 9, 2018 at 3:07 PM, Michael Allwright
> wrote:
> > Yes, it ended up in the development package in the do_install_append
> > attempt
>
> How did you confirm that (ie that the header ended up in the
> module-a-dev package) ?
In
On Mon, Jul 9, 2018 at 3:07 PM, Michael Allwright
wrote:
> Yes, it ended up in the development package in the do_install_append
> attempt
How did you confirm that (ie that the header ended up in the
module-a-dev package) ?
> , but I couldn't #include it in the second module (file didn't exist
>
Yes, it ended up in the development package in the do_install_append
attempt, but I couldn't #include it in the second module (file didn't exist
in the include search paths).
I would point out though, that I am interested in what is the correct way
to do this, and not just in finding some
On Mon, Jul 9, 2018 at 8:27 AM, Michael Allwright
wrote:
> Hello,
>
> I think it would be useful to extend the hello-mod recipe in meta-skeleton
> to demonstrate some slightly more complicated scenarios. For example, I am
> trying to find out how to have two external kernel modules A and B, where
Hello,
I think it would be useful to extend the hello-mod recipe in meta-skeleton
to demonstrate some slightly more complicated scenarios. For example, I am
trying to find out how to have two external kernel modules A and B, where
module B #includes a header file provided by module A.
I have
