[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
The attached patch makes strictwarn default, to get the old behavior,
use --disable-strictwarn. There are several patches in CVS which don't
compile with gcc and warnings enabled, i fixed one in file.c, one in
mouse.c, just to be hit by xmouse.c :P
Hopefully this patch will force more careful commits (Including myself,
I often had commited code with warnings myself.. Eric will tell you) :)
--
Elias Pschernig
Index: configure.in
===================================================================
RCS file: /cvsroot/alleg/allegro/configure.in,v
retrieving revision 1.83
diff -u -r1.83 configure.in
--- configure.in 28 Aug 2004 19:56:54 -0000 1.83
+++ configure.in 27 Sep 2004 14:51:55 -0000
@@ -109,8 +109,9 @@
dnl How strict should we be about compiler warnings
AC_ARG_ENABLE(strictwarn,
-[ --enable-strictwarn[=x] produce strict compiler warnings [default=no]],
-test "X$enableval" != "Xno" && allegro_strict_warnings=yes)
+[ --enable-strictwarn[=x] produce strict compiler warnings [default=yes]],
+test "X$enableval" != "Xno" && allegro_strict_warnings=yes,
+allegro_strict_warnings=yes,)
if test "X$allegro_strict_warnings" = "Xyes"; then
_warnmode="Building Allegro with strict warnings."