From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 69AC74226C for ; Tue, 1 Mar 2022 13:28:07 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id CE35C68B15F; Tue, 1 Mar 2022 15:28:04 +0200 (EET) Received: from mail8.parnet.fi (mail8.parnet.fi [77.234.108.134]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 4554768B0CD for ; Tue, 1 Mar 2022 15:27:58 +0200 (EET) Received: from mail9.parnet.fi (mail9.parnet.fi [77.234.108.21]) by mail8.parnet.fi with ESMTP id 221DRv4r017423-221DRv4s017423 for ; Tue, 1 Mar 2022 15:27:57 +0200 Received: from foo.martin.st (host-97-187.parnet.fi [77.234.97.187]) by mail9.parnet.fi (Postfix) with ESMTPS id 5D8CEA142C for ; Tue, 1 Mar 2022 15:27:56 +0200 (EET) Date: Tue, 1 Mar 2022 15:27:56 +0200 (EET) From: =?ISO-8859-15?Q?Martin_Storsj=F6?= To: FFmpeg development discussions and patches In-Reply-To: <18377e32-9223-6cec-3deb-5759d9b555fd@pocock.pro> Message-ID: References: <752868c0-25e3-8801-67fa-0a4ec1adb0c4@pocock.pro> <18377e32-9223-6cec-3deb-5759d9b555fd@pocock.pro> MIME-Version: 1.0 X-FE-Policy-ID: 3:14:2:SYSTEM Subject: Re: [FFmpeg-devel] [PATCH] fix build, avcodec: update OpenH264 header path X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Tue, 1 Mar 2022, Daniel Pocock wrote: > > > On 01/03/2022 10:19, Hendrik Leppkes wrote: >> On Tue, Mar 1, 2022 at 9:16 AM 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 >>> >>> OR >>> >>> #include >>> >>> 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? > > This patch is very trivial and doesn't attempt to support older releases > of OpenH264. So far, ffmpeg has supported a range of versions of OpenH264, from 1.3 up to the latest version. > Please keep in mind the OpenH264 code is patented .. and how does that differ from the code in libavcodec? > and not widely installed in Linux distributions. Developers have to > download it directly each time they include it in a project. > So there doesn't appear to be a compelling case to support many versions > concurrently. First off, supporting one or more versions is kinda essential for being able to track down any regression in the combination of the two projects. Then secondly, OpenH264 does provide binaries for the existing releases, with the extra benefit that if you have the users download the binary from Cisco, Cisco covers the patent license fee for that individual copy of the library. To be able to benefit from this, you need to build ffmpeg against one of the existing releases out there. So TL;DR, just because _you_ don't see a reason for supporting older releases, please don't deprive others of the ability to do that. So to support latest git master of OpenH264, we'd instead have to add a configure check to see what include path the library happens to use. // Martin _______________________________________________ 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".