* [Buildroot] Question Linux-Module infrastructure
[not found] <mailman.9992.1626731586.223516.buildroot@busybox.net>
@ 2021-07-20 5:03 ` Andreas Ziegler
2021-07-20 6:21 ` [Buildroot] [SOLVED] " Jacques Samoun
0 siblings, 1 reply; 4+ messages in thread
From: Andreas Ziegler @ 2021-07-20 5:03 UTC (permalink / raw)
To: buildroot
Hi Jacques,
On 2021-07-19 21:53, Jacques Samoun <jacques.samoun33@gmail.com> wrote:
> Hello,
>
> I am using external tree build in my project. Trying to add a linux
> kernel
> driver that i am developing.
> My problem is that, the sources of my driver are not flat but arranged,
> for
> various reasons in the following manner:
> <mydriver>
> <some files>
> <top makefile>
> +--- inc
> <shared includes>
> +--- user
> <files>
> <Makefile>
> +--- kernel
> <files>
> <Makefile>
>
> My hal.mk is (hal is the name of the package)
>
> HAL_VERSION = 1.0.0
> HAL_SITE = ../top/source/hal
> HAL_SITE_METHOD = local
You probably just need a statement to point the kernel build to the
correct subdirectory:
HAL_MODULE_SUBDIRS = kernel
Kind regards,
Andreas
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] [SOLVED] Re: Question Linux-Module infrastructure
2021-07-20 5:03 ` [Buildroot] Question Linux-Module infrastructure Andreas Ziegler
@ 2021-07-20 6:21 ` Jacques Samoun
0 siblings, 0 replies; 4+ messages in thread
From: Jacques Samoun @ 2021-07-20 6:21 UTC (permalink / raw)
To: buildroot
Hi Andreas,
Great, this wolves my problem.
Actually i was not too sure this SUBDIRS stuf was for .... now i got it :)
Thanks,
Jacques
On Tue, Jul 20, 2021 at 8:03 AM Andreas Ziegler <br015@umbiko.net> wrote:
> Hi Jacques,
>
> On 2021-07-19 21:53, Jacques Samoun <jacques.samoun33@gmail.com> wrote:
>
> > Hello,
> >
> > I am using external tree build in my project. Trying to add a linux
> > kernel
> > driver that i am developing.
> > My problem is that, the sources of my driver are not flat but arranged,
> > for
> > various reasons in the following manner:
> > <mydriver>
> > <some files>
> > <top makefile>
> > +--- inc
> > <shared includes>
> > +--- user
> > <files>
> > <Makefile>
> > +--- kernel
> > <files>
> > <Makefile>
> >
> > My hal.mk is (hal is the name of the package)
> >
> > HAL_VERSION = 1.0.0
> > HAL_SITE = ../top/source/hal
> > HAL_SITE_METHOD = local
>
> You probably just need a statement to point the kernel build to the
> correct subdirectory:
>
> HAL_MODULE_SUBDIRS = kernel
>
> Kind regards,
> Andreas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210720/f6233b6f/attachment-0001.html>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] Question Linux-Module infrastructure
@ 2021-07-19 16:16 ` Jacques Samoun
0 siblings, 0 replies; 4+ messages in thread
From: Jacques Samoun @ 2021-07-19 16:16 UTC (permalink / raw)
To: buildroot
Hello,
I am using external tree build in my project. Trying to add a linux kernel
driver that i am developing.
My problem is that, the sources of my driver are not flat but arranged, for
various reasons in the following manner:
<mydriver>
<some files>
<top makefile>
+--- inc
<shared includes>
+--- user
<files>
<Makefile>
+--- kernel
<files>
<Makefile>
My hal.mk is (hal is the name of the package)
HAL_VERSION = 1.0.0
HAL_SITE = ../top/source/hal
HAL_SITE_METHOD = local
$(eval $(kernel-module))
$(eval $(generic-package))
My problem is that, with the HAL_SITE above, everything is rsync'ed
correctly in the br/output dir, but the driver (*in the kernel subdir*)
fails to compile.
On the other hand, if HAL_SITE = ../top/source/hal/kernel
then obviously only a part of the files would be rsync'ed and the shared
inlcude files will be missing (|for example) .... but the kernel driver
will be build (and eventually fails because of the shared include files)
What am I missing ? this must be a small detail that i am completely
overlooking ...
Thanks,
Jacques
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210719/3e1fbd6a/attachment-0001.html>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] Question Linux-Module infrastructure
@ 2021-07-19 16:16 ` Jacques Samoun
0 siblings, 0 replies; 4+ messages in thread
From: Jacques Samoun @ 2021-07-19 16:16 UTC (permalink / raw)
To: buildroot
Hello,
I am using external tree build in my project. Trying to add a linux kernel
driver that i am developing.
My problem is that, the sources of my driver are not flat but arranged, for
various reasons in the following manner:
<mydriver>
<some files>
<top makefile>
+--- inc
<shared includes>
+--- user
<files>
<Makefile>
+--- kernel
<files>
<Makefile>
My hal.mk is (hal is the name of the package)
HAL_VERSION = 1.0.0
HAL_SITE = ../top/source/hal
HAL_SITE_METHOD = local
$(eval $(kernel-module))
$(eval $(generic-package))
My problem is that, with the HAL_SITE above, everything is rsync'ed
correctly in the br/output dir, but the driver (*in the kernel subdir*)
fails to compile.
On the other hand, if HAL_SITE = ../top/source/hal/kernel
then obviously only a part of the files would be rsync'ed and the shared
inlcude files will be missing (|for example) .... but the kernel driver
will be build (and eventually fails because of the shared include files)
What am I missing ? this must be a small detail that i am completely
overlooking ...
Thanks,
Jacques
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210719/3e1fbd6a/attachment-0002.html>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-07-20 6:21 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <mailman.9992.1626731586.223516.buildroot@busybox.net>
2021-07-20 5:03 ` [Buildroot] Question Linux-Module infrastructure Andreas Ziegler
2021-07-20 6:21 ` [Buildroot] [SOLVED] " Jacques Samoun
2021-07-19 16:16 [Buildroot] " Jacques Samoun
2021-07-19 16:16 ` Jacques Samoun
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.