[FFmpeg-devel] [PATCH] #define LAVF_API_MAX_STREAMS

Aurelien Jacobs aurel
Wed Aug 11 19:21:09 CEST 2010


We currently have quite a few new API (or API deprecation) in lavf/lavc
which are waiting for a major version bump to be fully enabled. Some of
those new API are fully functionnal and ready to be used, some of them
are work in progress that don't even compile for now (eg. AVPalette
All of them are currently protected by some check like:
So we now have quite of mess of MAJOR version check all around and it's
not always easy to say which one match which API change. Moreover, it's
not easy to enable just one of those API change to conduct some tests.
Just bumping the major lead to a non-compilable source tree.

So I propose to add one new define for each API transition we are
working on. This would allow to trivially test each transition
individually, and also to trivially re-schedule an (incomplete)
transition to next major bump when bumping major.

For example this allows testing the API transition with something like:
  ./configure --extra-cflags=-DLAVF_API_MAX_STREAMS=0

Attached patch does this for the currently worked on MAX_STREAMS
transition, and I plan to propose patches for other transitions if this
one is accepted.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: lavf_api_max_streams.diff
Type: text/x-diff
Size: 1508 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20100811/af9d74f3/attachment.diff>

More information about the ffmpeg-devel mailing list