Petro,
We don't generate a separate header package itself, but each kernel build package contains the partial build tree necessary to build out-of-tree modules.
There is a subdirectory in each build package called mbuild which can be extracted and referenced for all out-of-tree builds.
This build package is used internally for all vendor and platform-specific out-of-tree module builds and is the official interchange for module builds.
For an example of how they get used you can follow the trail of the following makefiles:
This platform needs these modules built against the given kernels:
This makefile then executes the kernel out-of-tree build script for the given modules and kernels:
This script automates the out-of-tree process for ONL kernels, if you would like to use it:
The important part is here, the extraction of the build tree from the kernel package itself used to build the modules:
If you want to add "normal" modules I would do it in this way.
If you want to add "complicated" module builds (like the Broadcom SDK's BDE modules) which need the location of the build tree then all you need is to set the $KERNEL location to
This is the same procedure we use to build our vendor systems.
Please let me if you have any additinonal questions.
Regards,
Jeff