From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16279] New: FFMPEG should require harfbuzz
Date: Fri, 17 Jan 2025 19:26:41 +0000 [thread overview]
Message-ID: <bug-16279-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=16279
Bug ID: 16279
Summary: FFMPEG should require harfbuzz
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: rubacha.jack03@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
Hi,
ffmpeg should require harfbuzz in some scenarios. Particularly in order to
have the drawtext filter, as seen here: https://trac.ffmpeg.org/ticket/10570
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-01-17 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 19:26 bugzilla [this message]
2025-01-17 21:46 ` [Buildroot] [Bug 16279] FFMPEG should require harfbuzz bugzilla
2025-01-18 21:13 ` bugzilla
2025-01-18 21:32 ` bugzilla
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=bug-16279-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox