On Tue, Apr 22, 2008 at 12:06:33AM +0000, Stuart Cassoff wrote: > I think that a debug flavor for Tcl is potentially useful to people who > write Tcl extensions or programs in Tcl. Debug flavors may be generally > useful for tracking down bugs in a port or even in OpenBSD itself. It isn't > always as easy as #defining DEBUG, though. :)
I mean 'DEBUG=-g make', which already does some secial things, and isn't any less/more easy than 'FLAVOR=debug make'. e.g. from the example I mentioned (audio/jack/Makefile): .ifdef DEBUG CONFIGURE_ARGS += --enable-debug .endif ... which is actually simpler than making an explicit FLAVOR ... > > Stu > > > >From: Jacob Meuser <[EMAIL PROTECTED]> > >To: [email protected] > >Subject: Re: Updated Tcl/Tk 8.5.2 ports. > >Date: Mon, 21 Apr 2008 21:42:41 +0000 > > > >On Mon, Apr 21, 2008 at 04:49:50PM -0400, Deanna Phillips wrote: > >> "Stuart Cassoff" <[EMAIL PROTECTED]> writes: > >> > >> > Polished install/Makefiles. > >> > Nicer install of include files. > >> > Added two flavors: debug (for the cautious), threaded (for the > >adventurous). > > > >hmm, do we want debug flavors? > > > >in the audio/jack port, if DEBUG is defined, debugging messages get turned > >on. I had a debug flavor, but if I'm going to debug a port, I want DEBUG > >defined during build anyway ... I think having ports turn on debugging > >when DEBUG is defined is a good "standard" for ports. I still see the > >usefulness of having separate packages though; being able to switch from > >one to the other easily ... maybe debug FLAVORS for all ports could be > >automatic, if DEBUG is defined? > > > >anyway, just some thoughts > > > > > >-- > >[EMAIL PROTECTED] > >SDF Public Access UNIX System - http://sdf.lonestar.org > > -- [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org
