Keep rules in v4l/Makefile from confusing kernel

From: Trent Piepho <xyzzy@speakeasy.org>

v4l/Makefile not only calls the kernel Makefile to do the module
building, but it is in turn included by the kernel Makefile.  This means
_all_ the rules in v4l/Makefile get used by the kernel Makefile when it
tries to build the modules.  Some of these rules, for files like .config,
Kconfig, .version, confuse the kernel building process.  The kernel make
thinks, "I need to remake _my_ Kconfig file because my .version file is
out of date." But that rule was never supposed to be used by the kernel,
it is just for v4l!

This is fixed by putting $(obj) in front of all these files' rules.  That
way the kernel will never think the rules refer to its files and try to
use them.

Really, this whole business of having the kernel Makefile include
v4l/Makefile is rather complex.  It might be a good idea to create
v4l/Kbuild, which the kernel will use in preference to v4l/Makefile, so
that we don't have to worry about v4l/Makefile getting used in two
different contexts.

Signed-off-by: Trent Piepho <xyzzy@speakeasy.org>

0 files changed, 0 insertions, 0 deletions