From: Pierre-Anthony Lemieux <pal@sandflow.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: correct libopenjpeg description
Date: Fri, 31 May 2024 08:37:16 -0700
Message-ID: <CAF_7JxA9SXnxJb091=JVvAjMpASs3YGeQ2oAnJWuoJjaMa-X5A@mail.gmail.com> (raw)
In-Reply-To: <20240531153133.539-1-ffmpeg@gyani.pro>
On Fri, May 31, 2024 at 8:32 AM Gyan Doshi <ffmpeg@gyani.pro> wrote:
>
> Decoding is no longer possible as the decoder wrapper was removed
> in 60ccb3fe78
> ---
> configure | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index 96b181fd21..6c5b8aab9a 100755
> --- a/configure
> +++ b/configure
> @@ -253,7 +253,7 @@ External library support:
> --enable-libopencore-amrwb enable AMR-WB decoding via libopencore-amrwb [no]
> --enable-libopencv enable video filtering via libopencv [no]
> --enable-libopenh264 enable H.264 encoding via OpenH264 [no]
> - --enable-libopenjpeg enable JPEG 2000 de/encoding via OpenJPEG [no]
> + --enable-libopenjpeg enable JPEG 2000 encoding via OpenJPEG [no]
LGTM
> --enable-libopenmpt enable decoding tracked files via libopenmpt [no]
> --enable-libopenvino enable OpenVINO as a DNN module backend
> for DNN based filters like dnn_processing [no]
> --
> 2.44.0
>
> _______________________________________________
> 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".
_______________________________________________
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:[~2024-05-31 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 15:31 Gyan Doshi
2024-05-31 15:37 ` Pierre-Anthony Lemieux [this message]
2024-05-31 15:51 ` Gyan Doshi
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='CAF_7JxA9SXnxJb091=JVvAjMpASs3YGeQ2oAnJWuoJjaMa-X5A@mail.gmail.com' \
--to=pal@sandflow.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