[Ffmpeg-devel] CONFIG_* vs HAVE_*
Diego Biurrun
diego
Sun Nov 12 17:29:52 CET 2006
On Sun, Nov 12, 2006 at 03:22:15PM +0000, M?ns Rullg?rd wrote:
> Diego Biurrun <diego at biurrun.de> writes:
>
> > On Sun, Nov 12, 2006 at 02:43:44PM +0000, M?ns Rullg?rd wrote:
> >> Diego Biurrun <diego at biurrun.de> writes:
> >>
> >> > On Wed, Nov 08, 2006 at 11:22:33AM +0000, M?ns Rullg?rd wrote:
> >> >>
> >> >> Fran?ois Revol said:
> >> >> >> I believe HAVE_ is for compiler-type features,
> >> >> >> (e.g. HAVE_STDLIB_H, HAVE_ALTIVEC, HAVE_FOUR_BYTE_INTS)
> >> >> >>
> >> >> >> and CONFIG_ is for user-level features -
> >> >> >> things that can be turned off and on by configure.
> >> >> >> (e.g. CONFIG_SWSCALER, CONFIG_USE_XV)
> >> >> >>
> >> >> >
> >> >> > Seems coherent.
> >> >>
> >> >> Yes, but that's not how the names are currently used, which is why I asked.
> >> >>
> >> >> > Also, HAVE_ is the prefix used by autoconf tests...
> >> >>
> >> >> True.
> >> >
> >> > So let's use that.
> >>
> >> The CPU features are oddly enough indicated by TARGET_* in config.mak
> >> and HAVE_* or ARCH_* in config.h.
> >
> > IIRC this is what autoconf uses, right?
>
> I don't remember. Either way, it's inconsistent and confusing.
Feel free to fix it as you see fit.
Diego
More information about the ffmpeg-devel
mailing list