Roland Mainz writes:
> Peter Memishian wrote:
> > "Uniformly for all AST libraries" isn't really uniform though, since
> > there's nothing inherently different about the AST libraries here -- quite
> > a few of our libraries consist of dozens to hundreds of source files.
> 
> Mhhh... what should I do in this case ? AFAIK options are:
> 1. Leave the Makefiles as they are
> 2. Rewrite Makefiles to store all *.o files in a flat layout (e.g.
> single directory) [Needs 5-8days to write, compile and test (largest
> part is to watch my machines to compile the stuff... ;-( )]
> 3. Convert more libraries to the "put object files in subdirs"-solution
> [e.g. you pick victim(s) and I'll switch them over... :-) ]
> 4. Any other ideas ?

I'm with meem on the earlier comment.  I see no reason at all to
impose structure on the 'pics' directories in any libraries.  It's
just a temporary repository of data, and not something that any human
ever needs to visit.  Flat is fine.

Adding logic to other libraries (as in 3) seems unhelpful.  It adds
new complexity to solve a non-problem.  (I think the fear _might_ be
having two .o names collide.  I'd venture to say that if you have
sources with foo/bar.c and blah/bar.c both producing bar.o, then
you've probably got much bigger design and readability problems to
contend with than just the obvious file name problems.)

Leaving these makefiles as they are (as in 1) isn't quite right,
because it means that this one area of the system is different from
the others.  That makes it harder to maintain.

So, as originally requested, I agree with (2).  I suppose I could be
persuaded that (1) is sufficient if nobody outside of this project
team will ever venture into these libraries enough to care.

-- 
James Carlson, Solaris Networking              <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to