On Mon, 5 Oct 1998, Mason Loring Bliss wrote:

> On Mon, Oct 05, 1998 at 01:35:40PM -0700, Bill Studenmund wrote:
> 
> > I too am not having this problem. So that's two who are, and two who
> > aren't.
> > 
> > Perry, are you using obj dir's? I am. Mason, Frederick, are y'all not
> > using obj dirs? I bet that's the reason for the observed difference.
> 
> I'm not doing anything out of the ordinary... Not cross-compiling, and
> I only keep one copy of the source around. (I'm starting to think that
> keeping two handy would be worthwhile - one raw -current and one stable
> -current.)
> 
> <searches for a clue, so as to better answer the question>

obj dirs are a feature where by all the actual compiling happens in a
subdirectory of the source. That way you don't have all the .o's
interspersed w/ the source.

It can also be set up so that the action happens in an port-specific
directory. Like my whole tree has obj.i386, obj.mac68k, and obj.macppc
directories. :-)

Everything make generates, like the .o's, .ln's .c's when they're from .y
files, etc., go into the obj directory (which is of course the
obj.$MACHINE directory if so configured).

This feature keeps things clean, and permits cross-compiling. :-) Also,
since the obj dir's can be symlinks to other places, you could work w/ a
read-only source directory.

Take care,

Bill