Messages in this thread | | | From | Daniel Phillips <> | Subject | Re: If you want kbuild 2.5, tell Linus | Date | Mon, 3 Jun 2002 16:54:41 +0200 |
| |
On Monday 03 June 2002 15:58, Keith Owens wrote: > Q07. Why is [b]zImage part of the config? > A07. In the current system, installation is a poor relation of the > build system. Each architecture has their own install targets > with their own special rules. None of the install targets check > that what is being installed was built correctly. > > In kbuild 2.5 the install target is a fully supported part of the > build. Not only is [b]zImage (and all the other targets) part of > the config, the config also supports installation to somewhere > other than /, plus optional rules for installing the config and > System.map at the same time as the kernel and modules. This > significantly improves support for cross compilation. > > A nice side effect of putting all the install information in > .config is that building a new kernel is as simple as > > cp previous_config .config > make ... defconfig installable && sudo make install
That simplification is appreciated, but I think that
make -f Makefile-2.5 bzImage
should still be allowed, call it compatibility glue if you like.
For what it's worth, I find it quite natural to have the build information in the .config and I was able to find my way to it without reading the docs. Still - when Makefile-2.5 becomes just plain Makefile, a lot of fingers are still going to want to type "make bzImage".
-- Daniel - 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/
| |