All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16288] New: mediastreamer does not build if it uses ffmpeg as a dependency
Date: Fri, 14 Feb 2025 06:37:17 +0000	[thread overview]
Message-ID: <bug-16288-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=16288

            Bug ID: 16288
           Summary: mediastreamer does not build if it uses ffmpeg as a
                    dependency
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: rubacha.jack03@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Mediastreamer uses FFMEPG_SWSCALE as an optional buildtime dependency.  If such
option is on (-DENABLE_FFMPEG=ON) then mediastreamer does not compile as it is
only compatible with ffmpeg 4.x.

Further, the Mediastreamer readme
(https://gitlab.linphone.org/BC/public/mediastreamer2) says ffmpeg support is
unmaintained.  Therefore it seems best to remove the mediastreamer comp-time
dependency on ffmpeg.

-- 
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

             reply	other threads:[~2025-02-14  6:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14  6:37 bugzilla [this message]
2025-02-14  6:41 ` [Buildroot] [Bug 16288] mediastreamer does not build if it uses ffmpeg as a dependency 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-16288-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.