Am Montag, den 20.03.2017, 12:25 +0100 schrieb Michael Olbrich: > On Mon, Mar 20, 2017 at 12:12:30PM +0100, Juergen Borleis wrote: > > On Monday 20 March 2017 12:00:57 Markus Niebel wrote: > > > [...] > > > +config KMSCUBE > > > + bool > > > + prompt "kmscube" > > > + select MESALIB > > > + select LIBDRM > > > + help > > > + kmscube is an application to test kms/drm drivers. > > > [...] > > > ---------------------------------------------------------------------------- > > > +# Prepare > > > +# > > > ---------------------------------------------------------------------------- > > > + > > > +KMSCUBE_CPPFLAGS += \ > > > + -I$(KERNEL_HEADERS_INCLUDE_DIR) > > > > If you need the kernel headers, then you also need a "select KERNEL_HEADER" > > in your 'kmscube.in' file. > > No, please don't. It really depends on the toolchain version. And the > kernel header package is explicitly built early so it can be enabled for > old toolchains. > What we should do is move the kernel headers kconfig option to the > platformconfig. >
Looked again through the code an noticed with the upgrade of the version the dep on kernel headers is gone, since the sources now using the headers provided by libdrm. Markus > Michael > _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de
