gnash-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-dev] Incorrect message when AGG is old...


From: strk
Subject: Re: [Gnash-dev] Incorrect message when AGG is old...
Date: Wed, 29 Aug 2007 11:29:54 +0200

On Mon, Aug 20, 2007 at 08:23:00PM +0200, Alfred M. Szmidt wrote:
>    >    s> Anyway, still interested in attempts to bild with an older AGG
>    >    s> ...
>    > 
>    >    As long as the particular 2.4 version contains the
>    >    render_scanlines_compound_layered template/class (normally
>    >    defined in agg_renderer_scanline.h) the AGG version should be
>    >    OK, so you could check for that if that's possible.
>    > 
>    >    Not sure if the compatibility layer is still worth it since
>    >    2.5 is now the current version.
>    > 
>    > It should be very trivial to do such a check:
>    > 
>    > AC_LANG([C++])
>    > AC_CHECK_LIB([some_crucial_function_in_libagg], [libagg], [],
>    >   AC_MSG_ERROR([you are missing libagg, please install it]))
>    > AC_CHECK_FUNC([render_scanlines_compound_layered], [],
>    >   AC_MSG_ERROR([you are using a version of libagg that does not work 
> with gnash]))
>    > 
>    > I don't know if this will work with C++'s template system though.
> 
>    Hardly, as the macro would try to link, w/out including any header.
> 
> Which doesn't matter, autoconf uses a dummy prototype of the function
> when testing if a symbol exists in a library. 

I mean, there's nothing to link, its *all* in header what we need in this case.

--strk;




reply via email to

[Prev in Thread] Current Thread [Next in Thread]