Some build environments do not support -xtype. Therefore
use -type instead.
Change-Id: I459bdd9e16dc31ea0b91d5f0cb86d4dabb1e3352
Signed-off-by: Bruce Levy <blevy@codeaurora.org>
Since commit <d5470d14431e9d39e> ("kbuild: re-implement
Makefile.headersinst without recursion"), the headers_install
excludes Kbuild from providing information regarding uapi headers.
In fact, it recursively pulls all the headers from a given path,
in this case techpack/*. This isn't correct as techpack/ may have
non-uapi headers as well, which shouldn't be considered. Hence,
strictly look for include/uapi/$dir directory for the uapi headers.
Change-Id: Ic7b3f927bc962729da1b87ed90e5f50a1e4cd5c5
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Due to path being inaccurate, the techpack folder was not being
compiled completely. Using techpack fixes this issue.
Change-Id: Id06927e5b4bfad0d5c8208b199d9d217abbf6306
Signed-off-by: Prakruthi Deepak Heragu <pheragu@codeaurora.org>
Enable tech packages to have kernel drivers that are physically
located in the kernel source tree but not present in the kernel
repository. This is done via a manifest line item to fetch a
techpackage-module into $KERNEL/techpack/$techpackage-module.
$KERNEL/techpack/Kbuild will automatically detect any
subdirectories and link them to the kernel's kbuild system.
The resulting layout of techpack within kernel source would be as
follows :-
kernel/
└── techpack/
├── Kbuild
├── stub/
│ ├── Makefile
│ ├── include/
│ │ └── uapi/
│ │ └── Kbuild
│ └── stub.c
└── techpackage-module/
├── Makefile
└── include/
└── uapi/
└── Kbuild
$KERNEL/techpack only contains Kbuild (no Makefile) at the
toplevel and this Kbuild takes care of both compiling the
subdirectories and of exporting the needed header files therein.
The reason for having only Kbuild at the top is that Kbuild
and Makefile cannot exist together in same directory and Makefile
doesn't cater to uapi header installation.
stub is an empty techpackage-module which serves both as a sample
layout and satisfies the requirement of kernel build system, by
providing necessary buit-in.o, when no other techpackage-module has
been pulled under techpack/.
$KERNEL/techpack/techpackage-module should have a Makefile at the
top and Kbuild under $KERNEL/techpack/techpackage-module/include/uapi
directory. The uapi headers pertaining to a techpackage-module
should reside under $KERNEL/techpack/techpackage-module/include/uapi
and associated Kbuild should have necessary rules to export it.
Change-Id: I0d0ced38566907d2074831edde0934833f666eff
Signed-off-by: Bryan Huntsman <bryanh@codeaurora.org>
