All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacques Samoun <jacques.samoun33@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question Linux-Module infrastructure
Date: Mon, 19 Jul 2021 19:16:56 +0300	[thread overview]
Message-ID: <CACaKL1z3AucmvN0SXF=E09fdTRF+fOfvLvBOPY_ogAo717NOKA@mail.gmail.com> (raw)

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>

WARNING: multiple messages have this Message-ID (diff)
From: Jacques Samoun <jacques.samoun33@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question Linux-Module infrastructure
Date: Mon, 19 Jul 2021 19:16:56 +0300	[thread overview]
Message-ID: <CACaKL1z3AucmvN0SXF=E09fdTRF+fOfvLvBOPY_ogAo717NOKA@mail.gmail.com> (raw)
Message-ID: <20210719161656.VNnizS3q4KgwmLW7vUedH8m1MujoJH0En_WvU3GCI3o@z> (raw)

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>

             reply	other threads:[~2021-07-19 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 16:16 Jacques Samoun [this message]
2021-07-19 16:16 ` [Buildroot] Question Linux-Module infrastructure Jacques Samoun
     [not found] <mailman.9992.1626731586.223516.buildroot@busybox.net>
2021-07-20  5:03 ` Andreas Ziegler

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='CACaKL1z3AucmvN0SXF=E09fdTRF+fOfvLvBOPY_ogAo717NOKA@mail.gmail.com' \
    --to=jacques.samoun33@gmail.com \
    --cc=buildroot@busybox.net \
    /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.