[wplug] Software builds.

[Diana A. Clarion]

It all depends on the organization of the source, really.  Packages like
gcc and glibc "strongly recommend" (read: require) that you set up a
separate build directory, i.e.

tar xzf gcc-x.y.tar.gz
cd gcc-x.y
../configure <arguments>
make bootstrap

whereas most other packages I've built don't care *where* you build, and
a few don't even *like* the build-directory method.

The stuff I've written has been simple enough that I can use the
build-in-place method.

DAC

On Fri, 2007-02-09 at 22:33 -0500, kabel wrote:
> A professor of mine recently got on my case as to how I build software.. he 
> advocates two directories, one for source, one for builds.  Packages get 
> their own subdirectory in each, with source going in the appropriate subdir. 
> and builds done in the other.  
> 
> I've never heard of doing it this way, and he may well have been referring to 
> a specific case, but does anyone else do this?  
> 
> What other good practices have I missed out on along these lines?
> 
> kabel
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug