![]() | |||||||||||
Messages in this thread |
On Fri, 28 Dec 2001 20:21:39 -0800, Mike Castle <dalgoda@ix.netcom.com> wrote: >On Fri, Dec 28, 2001 at 10:58:03PM -0500, Legacy Fishtank wrote: >> s/break/update dependencies/ >> >> I assumed this was blindingly obvious, but I guess not. > >To YOU and other kernel hackers, yes. > >But not to everyone. > >Plus, as I understand it, it will be faster to: > >apply a patch and rebuild with kbuild 2.5 > >than to: > >apply a patch, make dep && make bzImage. > >Correct? As long as the patch does not change an include file that is used a lot, yes, a patch and make will be significantly faster using kbuild 2.5. What Mr. Fishtank seems to overlook is that kbuild 2.5 is far more flexible and accurate than 2.4, including features that lots of people want, like separate source and object trees. Now that the overall kbuild design is correct, the core code can be rewritten for speed. And that will be done a couple of weeks after kbuild 2.5 goes into the kernel, then I expect kbuild 2.5 to be faster than kbuild 2.4 even on full builds. - 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/ | ||||||||||
| Last update: 2005-03-22 13:14 [from the cache] ©2003-2008 | |||||||||||