From: "Guo, Yejun" <yejun.guo-at-intel.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 FFmpeg 1/20] configure: add tokenizers-cpp support
Date: Mon, 12 May 2025 09:54:10 +0000
Message-ID: <PH7PR11MB59575A99F31F63F53283A6AAF197A@PH7PR11MB5957.namprd11.prod.outlook.com> (raw)
In-Reply-To: <003501db91f5$8c7e15d0$a57a4170$@gmail.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> m.kaindl0208@gmail.com
> Sent: Tuesday, March 11, 2025 3:50 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v2 FFmpeg 1/20] configure: add tokenizers-
> cpp support
>
> Signed-off-by: MaximilianKaindl <m.kaindl0208@gmail.com>
> ---
> configure | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/configure b/configure
> index 04b83a8868..7219faeaf2 100755
> --- a/configure
> +++ b/configure
> @@ -285,6 +285,7 @@ External library support:
> --enable-libtls enable LibreSSL (via libtls), needed for https support
> if openssl, gnutls or mbedtls is not used [no]
> --enable-libtorch enable Torch as one DNN backend [no]
> + --enable-libtokenizers enable tokenizers-cpp library [no]
Not finished all the review yet, I have several comments in some of the commits.
Is libtokenizers a popular library? How to install? Please also add in commit comments, thanks.
_______________________________________________
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".
prev parent reply other threads:[~2025-05-12 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 19:49 m.kaindl0208
2025-05-12 9:54 ` Guo, Yejun [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=PH7PR11MB59575A99F31F63F53283A6AAF197A@PH7PR11MB5957.namprd11.prod.outlook.com \
--to=yejun.guo-at-intel.com@ffmpeg.org \
--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