On 4/10/24 07:11, Andreas Rheinhardt wrote:
I don't
see a simplification of the Makefile.
Relevant part from the diff:
--- a/libavcodec/bsf/Makefile
+++ b/libavcodec/bsf/Makefile
@@ -45,5 +45,3 @@ OBJS-$(CONFIG_VP9_SUPERFRAME_BSF) +=
bsf/vp9_superframe.o
OBJS-$(CONFIG_VP9_SUPERFRAME
On 4/9/24 17:04, Lynne wrote:
LGTM.
That's how I wrote the AAC patchset as well.
Thank you for the review, Lynne.
What is the next step? I do not have commit access.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/lis
Removes the special -I flag specified in the avcodec/bsf/ subdirectory.
This makes code copy-pastable to other parts of the ffmpeg codebase, as
well as simplifying the build script.
It also reduces ambiguity, since there are many instances of same-named
header files existing in both libavformat/
On Sun, Aug 10, 2014 at 1:48 AM, Jean-Yves Avenard
wrote:
> Then it becomes unreasonable for a piece of software to be compatible
> with multiple version of the same library, and support all of those.
>
IMO it's not worth the effort to support multiple versions of the same
library. If you want t
On Sun, Aug 10, 2014 at 12:01 AM, Matthias Urlichs
wrote:
> Jean-Yves Avenard:
> > Including rename of constants (code enums id for example).
>
> Another nail in libav's coffin, then.
>
> IMHO it's reasonable to expect core APIs to be upwards-compatible and keep
> deprecated interfaces around for
