[asterisk-dev] [asterisk-commits] russell: trunk r89615 - in /trunk: configure configure.ac

Luigi Rizzo rizzo at icir.org
Tue Nov 27 08:52:27 CST 2007

On Tue, Nov 27, 2007 at 08:03:58AM -0600, Kevin P. Fleming wrote:
> Russell Bryant wrote:
> >> AST_EXT_LIB_CHECK([PRI], [pri], [pri_new_bri], [libpri.h],,,[20071125])
> >> AST_EXT_LIB_CHECK([PRI], [pri], [pri_keypad_facility], [libpri.h],,,[20071010])
> >> AST_EXT_LIB_CHECK([PRI], [pri], [pri_somethingelse], [libpri.h],,,[20010203])
> It would be preferable to use feature testing directly and create HAVE_
> macros for those features and not care about release dates or anything
> without real meaning.

Either way. I think it really depends on the package.

Your suggestion is optimal when features are mutually independent
(and in fact this is what i have done for SDL, SDL_IMAGE, SDL_TTF).

Version number/release dates are probably more appropriate for tools
with incremental features (so you can check VERSION >= XXX, e.g.
we do that in configure.ac) or for those where the feature set is
not well defined across versions (in which case you probably need
an exact match).


More information about the asterisk-dev mailing list