Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
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 22:50:57 +0100
Message-ID: <20220301215057.GW2829255@pb2> (raw)
In-Reply-To: <752868c0-25e3-8801-67fa-0a4ec1adb0c4@pocock.pro>


[-- Attachment #1.1: Type: text/plain, Size: 1756 bytes --]

On Tue, Mar 01, 2022 at 09:16:17AM +0100, Daniel Pocock 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.
> 
> Regards,
> 
> Daniel
> 
> -- 
> Debian Developer
> https://danielpocock.com

>  configure                   |    2 +-
>  libavcodec/libopenh264.c    |    4 ++--
>  libavcodec/libopenh264dec.c |    4 ++--
>  libavcodec/libopenh264enc.c |    4 ++--
>  4 files changed, 7 insertions(+), 7 deletions(-)
> 281ee5285fd9f4b7f9ae94f3786e0006de037b6a  0001-avcodec-update-OpenH264-header-path.patch
> From 6736ae3d20db9cb79b328c6e3e9080c42c6216d4 Mon Sep 17 00:00:00 2001
> From: Daniel Pocock <daniel@pocock.pro>
> Date: Tue, 1 Mar 2022 09:09:00 +0100
> Subject: [PATCH] avcodec: update OpenH264 header path

breaks build here on ubuntu x86_64

ERROR: openh264 not found using pkg-config

If you think configure made a mistake, make sure you are using the latest
version from Git.  If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.libera.chat.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.


[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Homeopathy is like voting while filling the ballot out with transparent ink.
Sometimes the outcome one wanted occurs. Rarely its worse than filling out
a ballot properly.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

      parent reply	other threads:[~2022-03-01 21:51 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
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 [this message]

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=20220301215057.GW2829255@pb2 \
    --to=michael@niedermayer.cc \
    --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