[FFmpeg-cvslog] r17168 - in trunk/libavcodec: vdpau.c vdpau.h vdpau_pixfmt.h xvmc.c xvmc_pixfmt.h xvmc_render.h

[Aurelien Jacobs]

Diego Biurrun wrote:

> On Thu, Feb 12, 2009 at 02:09:02AM +0100, Aurelien Jacobs wrote:
> > diego wrote:
> > 
> > > Log:
> > > Rename [...] and vdpau.h --> vdpau_pixfmt.h
> > 
> > This is broken. Make install won't work anymore.
> > Moreover, strictly speaking, you are breaking public API, and
> > thus this would require a major version bump.
> 
> Hmmm....

This don't really tells me much...

Anyway, the situation is quite clear:
 - either you consider this header part of public API, and then
   you can't rename it without a major version bump
 - or you don't consider it part of public API, and then it
   must not be installed
I can't see any other possibility.

> > But anyway, it seems that vdpau*.h should really not be part
> > of public API anyway, so better stop installing it right now.
> 
> How else are applications supposed to use vdpau with FFmpeg then?

The same way they access VA-API or xvmc. Through a common API.
See the many recent post discussing implementation of HWAccel on
ffmpeg-devel.
The following thread, among others, contains various interesting
ideas:
[FFmpeg-devel] [PATCH][7/8] Add VA API accelerated H.264 decoding

Anyway, it should be quite clear to anyone reading ffmpeg-devel
that hardware acceleration through ffmpeg is currently a moving
target, and the API to use it is bound to change quite a lot
before it stabilize. So exporting anything to the outside world
right now seems pretty much useless.

Aurel