Date: Wed, 6 Jan 1999 11:29:09 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Nate Eldredge <nate AT cartsys DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Announce: Allegro 3.1
In-Reply-To: <3692BEEE.79E6FF53@cartsys.com>
Message-ID: <Pine.SUN.3.91.990106112829.8103G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Tue, 5 Jan 1999, Nate Eldredge wrote:

> IMHO, warnings are for developers, not for users compiling.

I agree.  And since Allegro is one of the few packages which wants to
be built by non-developers, it strikes me that arranging for the
``normal'' build to not use *any* warnings, not even -Wall, would be
The Right Thing.  Once the package has been developed and released,
there's no need to use -Wall, since any bugs that those warnings might
find are supposed to be squashed already.

So, you could have a build-debug: target in the Makefile that would
use any level of warnings you see fit, but the usual build will not
use that target.