[vlc-devel] [PATCH 1/3] Modifications to the VLC core to create a special VAAPI chroma

Etienne Membrives etienne at membrives.fr
Wed Aug 5 14:55:31 CEST 2009


Hello,

Rémi Denis-Courmont wrotes :
> On Wed,  5 Aug 2009 13:17:05 +0200, Etienne Membrives
> <etienne at membrives.fr> wrote:
>> +AS_IF([test "${enable_vaapi}" = "yes"], [
>> +  AS_IF([test "x${have_avcodec}" = "xyes"], [
>> +  PKG_CHECK_MODULES(VAAPI,[libva],
>> +      [
>> +      AC_CHECK_HEADERS(va/va.h X11/Xlib.h)
>> +      AC_DEFINE(HAVE_AVCODEC_VAAPI, 1, [Define if you have VAAPI])
>> +      VLC_ADD_LIBS([avcodec],[$VAAPI_LIBS -lva-x11])
>> +      VLC_ADD_LIBS([avcodec],[${X_LIBS} ${X_PRE_LIBS} -lX11])
>> +      VLC_ADD_PLUGIN([vaapi])
>> +      VLC_ADD_PLUGIN([vaapi_i420])
> 
> Pardon my ignorance but why is the vaapi plug-in dependent on ffmpeg?

In this implementation, it is ffmpeg (in fact, libavcodec) that issues
API calls to decode pictures using VAAPI. Then, vaapi structures are
retrieved by the avcodec plug-in. The vaapi plug-in (which is a video
output) thus needs avcodec to be used and don't have any utility otherwise.

So, I put this dependence uniquely because, now, using ffmpeg is
necessary to use vaapi in VLC.

Regards,
-- 
Etienne Membrives


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20090805/62142d17/attachment.sig>


More information about the vlc-devel mailing list