On Tue, 19 Nov 2002, Larry McVoy wrote: > On Tue, Nov 19, 2002 at 03:22:45PM -0500, Richard B. Johnson wrote: > > On Tue, 19 Nov 2002, Sam Ravnborg wrote: > > > > > Based on some initial work by Kai Germaschewski I have made a > > > working prototype of separate obj/src tree. > > > > > > Usage example: > > > #src located in ~/bk/linux-2.5.sepobj > > > mkdir ~/compile/v2.5 > > > cd ~/compile/v2.5 > > > sh ../../kb/v2.5/kbuild > > > > [SNIPPED...] > > > > I have a question; "What problem is this supposed to solve?" > > This looks like a M$ism to me. Real source trees don't > > look like this. If you don't have write access to the source- > > code tree, you are screwed on a real project anyway. That's > > why we have CVS, tar and other tools to provide a local copy. > > It can be really nice to maintain a bunch of different architectures at > the same time from the same tree. It also makes it really easy to > "clean" a tree. > > On the other hand, I do wonder whether ccache could be used to get the > same effect. Sam?
ccache helps a lot if you change your .config back to one previously compiled, but it still doesn't offer you the option to keep multiple .configs around at the same time. Also, of course it doesn't help with keeping the source tree clean of non-source files ;) Wrt the original patch, I like it, one preliminary comment is that I think symlinks are nicer than copying. They are faster, shouldn't cause any trouble on NFS, make uses "stat" and not "lstat", so it gets the timestamps right, too. And if you edit a Makefile/Kconfig in the source tree, you rather want that to take effect immediately, I guess ;) --Kai ------------------------------------------------------- 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
