X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C89119.1DDD6888@onstor-exch02.onstor.net>; Fri, 28 Mar 2008 14:17:24 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Debug build symbol for SSC builds
Date: Fri, 28 Mar 2008 14:17:24 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E038F8FAA@onstor-exch02.onstor.net>
In-Reply-To: <20080328135232.22ba6db8@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Debug build symbol for SSC builds
Thread-Index: AciRFaUuMTsVYLuYTVCQOBOlG/bS4gAAwesA
From: "James Kahn" <james.kahn@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>


If you have conditional code, you only have "#ifdef FS_DEBUG" on SSC.
For FP and TXRX, you use "#ifdef DEBUG".

It would be nice if we had some consistent mechanism to detect dbg vs.
opt builds at compile time.

That's all,
Jim





-----Original Message-----
From: Andy Sharp=20
Sent: Friday, March 28, 2008 1:53 PM
To: James Kahn
Cc: dl-Software
Subject: Re: Debug build symbol for SSC builds

On Fri, 28 Mar 2008 13:45:45 -0700 "James Kahn" <james.kahn@onstor.com>
wrote:

>=20
> I would like to propose the SSC_DEBUG symbol be used to identify debug
> builds from opt builds on the
> SSC processor.  The existing system for SSC builds is FS_DEBUG which
> does not seem appropriate.
>=20
> DEBUG cannot be used because it conflicts with the open-source code.
> (DEBUG is used for
> FP and TXRX debug builds as this issue does not exist there.)
>=20
>=20
> So, I would appreciate your comments on this suggestion to create a
> SSC debug build symbol.

I'm not sure what you mean by symbol.  Do you mean C preprocessor
macro, and if so, in what capacity?  How would it differ from the
semantics of the VARIANT environment variable?
