From: Hendrik Leppkes <h.leppkes@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] fix build, avcodec: update OpenH264 header path
Date: Tue, 1 Mar 2022 10:19:30 +0100
Message-ID: <CA+anqdyYra-ih+-Q9+mt9wws7_MGApFgySEG3BKeV_HkY73Jkw@mail.gmail.com> (raw)
In-Reply-To: <752868c0-25e3-8801-67fa-0a4ec1adb0c4@pocock.pro>
On Tue, Mar 1, 2022 at 9:16 AM Daniel Pocock <daniel@pocock.pro> wrote:
>
>
> This updates the locations searched for the OpenH264 headers to be
> consistent with upstream
>
> Discussed here:
> https://github.com/cisco/openh264/pull/3415
>
> Due to the change in the pkgconfig file, it is possible to compile with
> either:
>
> #include <openh264/codec_api.h>
>
> OR
>
> #include <codec_api.h>
>
> but in this patch, I used the former.
>
Which releases of the library have the updated location? Will older
releases still work, if so, which?
As far as I can see, the change is days old and not in any release, so
committing this now would break compatibility with anything but
OpenH264 git master? Is that correct?
- Hendrik
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-03-01 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 8:16 Daniel Pocock
2022-03-01 9:19 ` Hendrik Leppkes [this message]
2022-03-01 10:14 ` Daniel Pocock
2022-03-01 13:27 ` Martin Storsjö
2022-03-01 15:13 ` Daniel Pocock
2022-03-01 15:29 ` Martin Storsjö
2022-03-01 21:50 ` Michael Niedermayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+anqdyYra-ih+-Q9+mt9wws7_MGApFgySEG3BKeV_HkY73Jkw@mail.gmail.com \
--to=h.leppkes@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git