On Friday 13 October 2006 14:11, Markus Gothe wrote:
> Modified files:
> . : ChangeLog configure.ac
>
> Log message:
> Die on --enable-strict && --enable-renderer=agg, because compilation
> will fail.
I wonder if this is the right thing to do. If we allow people to pass a
combination of these options, perhaps someone will be motivated to fix
said AGG code. (That is, of course, assuming it has not already been
fixed.)
Bastiaan
> Index: configure.ac
> ===================================================================
> RCS file: /sources/gnash/gnash/configure.ac,v
> retrieving revision 1.154
> retrieving revision 1.155
> diff -u -b -r1.154 -r1.155
> --- configure.ac 12 Oct 2006 16:03:12 -0000 1.154
> +++ configure.ac 13 Oct 2006 12:11:56 -0000 1.155
> @@ -33,7 +33,7 @@
> dnl also makes it possible to release a modified version which
> carries dnl forward this exception.
>
> -dnl $Id: configure.ac,v 1.154 2006/10/12 16:03:12 strk Exp $
> +dnl $Id: configure.ac,v 1.155 2006/10/13 12:11:56 nihilus Exp $
>
> AC_PREREQ(2.50)
> AC_INIT(gnash, 0.7.1-cvs)
> @@ -622,7 +622,9 @@
> *) AC_MSG_ERROR([bad value ${enableval} for --enable-strict
> option]) ;; esac], [strict=no])
>
> -
> +if test x"$strict" = x"yes" -a x"$renderer" = x"agg"; then
> + AC_MSG_ERROR([agg renderer will fail with --enable-strict.]);
> +fi
>
> # We want warnings, lots of warnings :-)
> if test x"$GCC" = x"yes"; then
>
Bastiaan
_______________________________________________
Gnash-commit mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnash-commit
