Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: richardssam via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: richardssam <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] av_filter/vf_opencolorio: libopenimage was added in error as part of the ocio filter, just cleaning it up. (PR #21771)
Date: Tue, 17 Feb 2026 09:11:16 -0000
Message-ID: <177131947717.25.4719686022525481912@29965ddac10e> (raw)

PR #21771 opened by richardssam
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21771
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21771.patch

Just noticed that the OCIO filter PR #21611 had added an extra line for non-existant external library libopenimage which was completely un-necessary.

Wanted to clean it up before somebody has to diagnose what its there for.



>From 726b9c3b3f0be44a9f41c8124fb8217c40303220 Mon Sep 17 00:00:00 2001
From: "Sam.Richards@taurich.org" <Sam.Richards@taurich.org>
Date: Mon, 16 Feb 2026 14:32:17 +0000
Subject: [PATCH] libopenimage was added in error as part of the ocio filter,
 just cleaning it up.

Signed-off-by: Sam.Richards@taurich.org <Sam.Richards@taurich.org>
---
 configure | 1 -
 1 file changed, 1 deletion(-)

diff --git a/configure b/configure
index 8a397598cd..3984bd83d9 100755
--- a/configure
+++ b/configure
@@ -2049,7 +2049,6 @@ EXTERNAL_LIBRARY_LIST="
     liboapv
     libopencv
     libopencolorio
-    libopenimage
     libopenh264
     libopenjpeg
     libopenmpt
-- 
2.52.0

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

                 reply	other threads:[~2026-02-17  9:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=177131947717.25.4719686022525481912@29965ddac10e \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=code@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