[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-20 Thread Alex Riesen
On Wed, Nov 20, 2002 at 02:10:03PM +0100, Alex Riesen wrote: > On Tue, Nov 19, 2002 at 09:11:10PM +0100, Sam Ravnborg wrote: > > The kbuild shell script takes a verbatim copy of all Makefiles, > > all Kconfig files and all defconfigs. I did not even look into > > using symlinks, I was not sure how

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-20 Thread Miles Bader
David Woodhouse <[EMAIL PROTECTED]> writes: > Of course it's a useful feature. Definitely. I already use home-grown scripts to maintain multiple object-trees, with the sources symlinked to a single source tree, because I generally maintain several different platforms simultaneously. Having one s

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-20 Thread Alex Riesen
On Tue, Nov 19, 2002 at 09:11:10PM +0100, Sam Ravnborg wrote: > The kbuild shell script takes a verbatim copy of all Makefiles, > all Kconfig files and all defconfigs. I did not even look into > using symlinks, I was not sure how they work across NFS > and the like. But Kconfigs and defconfigs bel

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Geert Uytterhoeven
On Tue, 19 Nov 2002, Daniel Jacobowitz wrote: > On Tue, Nov 19, 2002 at 03:46:28PM -0500, Richard B. Johnson wrote: > > On Tue, 19 Nov 2002, Sam Ravnborg wrote: > > > > > On Tue, Nov 19, 2002 at 03:22:45PM -0500, Richard B. Johnson wrote: > > > > I have a question; "What problem is this supposed t

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Daniel Jacobowitz
On Tue, Nov 19, 2002 at 03:46:28PM -0500, Richard B. Johnson wrote: > On Tue, 19 Nov 2002, Sam Ravnborg wrote: > > > On Tue, Nov 19, 2002 at 03:22:45PM -0500, Richard B. Johnson wrote: > > > I have a question; "What problem is this supposed to solve?" > > > > Two problems (at least): > > > > 1)

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Brad Hards
-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 sou

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Kai Germaschewski
On Tue, 19 Nov 2002, Richard B. Johnson wrote: > I think all you did was increase the compile time by writing > output files to different directories than the ones currently > in cache. There are a lot of negatives. It would be a shame for > you to waste a great deal of time on something that woul

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Kai Germaschewski
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 e

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Richard B. Johnson
On Tue, 19 Nov 2002, Sam Ravnborg wrote: > On Tue, Nov 19, 2002 at 03:22:45PM -0500, Richard B. Johnson wrote: > > I have a question; "What problem is this supposed to solve?" > > Two problems (at least): > > 1) You want to compile your kernel based on two different configurations, > but sharing

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Richard B. Johnson
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 h

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Sam Ravnborg
On Tue, Nov 19, 2002 at 02:48:09PM -0600, Kai Germaschewski wrote: > 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 rig

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread David Woodhouse
[EMAIL PROTECTED] said: > Others that have asked for separate obj dir may step in here, > explaining why they thougt it was good. Why? The only person arguing against it is RBJ, and people only ever read his mails for the amusement value. Of course it's a useful feature. -- dwmw2 ---

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Sam Ravnborg
On Tue, Nov 19, 2002 at 03:46:28PM -0500, Richard B. Johnson wrote: > Different configurations are handled with different ".config" > files. And different .config files results in different kernels. Please note that .config files are also located in OBJTREE. Cosider something like the following:

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Sam Ravnborg
On Tue, Nov 19, 2002 at 12:31:15PM -0800, Larry McVoy wrote: > 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

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Larry McVoy
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 > > m

[kbuild-devel] Re: [RFC/CFT] Separate obj/src dir

2002-11-19 Thread Sam Ravnborg
On Tue, Nov 19, 2002 at 03:22:45PM -0500, Richard B. Johnson wrote: > I have a question; "What problem is this supposed to solve?" Two problems (at least): 1) You want to compile your kernel based on two different configurations, but sharing the same src. No need to have a duplicate of all src. -