[Buildroot] [PATCH v4] linux-headers: allow use of headers from kernel "package" selected

[Peter Korsgaard <peter@korsgaard.com>]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Peter,
 > On Mon, 18 Jan 2016 23:21:08 +0100, Peter Korsgaard wrote:

 >> > I also don't like the way the patch is implemented, but I think the
 >> > problem raised by this patch is real. Sometimes people have kernel
 >> > sources that contain some custom kernel headers needed for their
 >> > userspace libraries/applications, and we have no mechanism to allow
 >> > them to use their custom kernel source for the linux-headers package,
 >> > which is a bit annoying.
 >> 
 >> Yeah, true. It does require that these custom header files are really
 >> exported (so they get installed by headers_install) which in my
 >> experience is not always the case.
 >> 
 >> What I have told people to do in the past instead is to either copy the
 >> needed definitions into their user space code or add
 >> -I$(LINUX_DIR)/include (if they build their kernel in Buildroot) like
 >> E.G. xdriver_xf86-video-imx does it.

 > Yes, I know there are ways around it.

But these "workarounds" are the only real solutions if you want to be
able to use existing binary toolchains.


 > But it does seem weird to many users that the "linux" package provides
 > some many possibilities for fetching/patching the kernel, and still the
 > linux-headers package downloads a completely different kernel version,
 > with less possibilities of using a custom version.

So perhaps we need an option to use the linux source for our kernel
headers? It does mean that people need to jump back and forth between
the toolchain and linux menus.

-- 
Venlig hilsen,
Peter Korsgaard