On Fri, Jan 17, 2003 at 10:36:54AM -0600, Kai Germaschewski wrote:
> > Isn't all of this in .depend?
>
> In 2.5 things work differently, so no.
The longer answer, if you feel bored :-)
In 2.5 kbuild generate a file that list all dependencies:
.foo.o.cmd
This file is generated the first time the file is compiled, and contains
dependencies too all included files + all referred CONFIG_* options.
What to keep in mind is that make does NOT know the dependencies when run
the very first time. Thats because there is no need to generate the
.foo.o.cmd file when the .o file does not exist - make will build it no
matter what.
Therefore if foo.c depends on <linux/whatever.h> make will not
see this dependency, and gcc will complain.
Though - at the second run make will know the dependency and 'get' the file.
Kconfig files are special in the sense that we do not always check
the full dependency on them.
We have autoconf.h, config/MARKER and more magic involved here.
Since kconfig does not generate a .config.cmd when it fails to locate
a Kconfig file, it would not help to clean up this - with respect to
BK/CVS integration.
HTH,
Sam - kbuild apprentice ;-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jan 23 2003 - 22:00:17 EST