-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Nov 2002 07:54, Sam Ravnborg wrote: > But my point is that there is a good use of different configurations > based on the same src. I think that your example for testing is the most valid one.
In development, you normally have different source trees (hardlinked if you don't have a terabyte of hard drive space to spare), and use an editor that breaks hard-links (eg, emacs). You might as well build in the source directory, since you'll likely keep reworking it. In release testing (aka release engineering, or more accurately: release fumbling-in-the-dark), you need to test a few different configurations. Sure, you could just build a set of symlink or hardlink trees, but it'd be very useful to be able to "make multiconfigs" and have a representative set of kernels built (either for later testing, or at least to ensure that the new kernel will build without modules, without networking, without IDE, and so on). Sure, it will take a while if you build everything, but that is why God^WTridge gave us ccache. Brad - -- http://linux.conf.au. 22-25Jan2003. Perth, Aust. I'm registered. Are you? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE92rNGW6pHgIdAuOMRAmcDAKCnzBOh6/6+zouOlM2bi1z2mcEmSACghEnp MzXw5OsNmbZfzBMVGrFmNr0= =7DkQ -----END PGP SIGNATURE----- ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
