Roland Mainz writes:
> > So, create your own project-related environment variable and use that
> > in the makefiles.
>
> Umpf... that's exactly what I'd like to avoid: Create yet another
> project-specific debugging variable. IMHO it may be nice to have one
> switch for all projects within OS/Net...
One problem with that strategy is that, assuming things are well-
designed, it's seldom helpful to enable "aggressive debugging" in
anything other than one's own project because effective use of that
sort of mode usually implies an intimacy with the code itself.
Enabling it across all of ON in one shot seems particularly unhelpful,
except maybe for the omniscient. ;-}
At least in the projects I've worked on, I've needed two basic kinds
of debug:
- Stuff that shouldn't be used in ordinary operation (because, for
example, it spams log files or greatly reduces performance), but
will reveal important details that can diagnose problems in the
field. This needs to be compiled in at all times and enabled by
some run-time option. And in many cases it may be obviated by
dtrace.
- Stuff that's internal to the development task at hand and is
discarded afterward. This can be enabled by any sort of crufty
means, including checking out the Makefile locally and tweaking
it.
I haven't really encountered a need for build-time enabling of special
debug features that have a more substantial or system-wide support
infrastructure than that. I guess your mileage will vary, so if you
see an obvious gap here, feel free to propose something more concrete.
--
James Carlson, KISS Network <[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
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
