From: Kieran Kunhya <kieran618@googlemail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] Move sdr within the libavradio repository
Date: Fri, 28 Jul 2023 11:39:30 +0100
Message-ID: <CABGuwE=McK8aAw-unz1uiJaNsXaMniPB77jm=rK+DGBsW0s7xA@mail.gmail.com> (raw)
In-Reply-To: <20230727223837.3970793-2-michael@niedermayer.cc>
On Thu, Jul 27, 2023 at 11:39 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> This moves sdr back from libavradio into libavdevice & libavformat
> (inside the libavradio repository)
>
> People originally wanted this code in a libavradio library but recently
> suggested that sdr should have no impact on other things in FFmpeg.
> libavradio has a substantial impact as it will result in distributions
> packaging a new library.
>
> Also there is currently no API specific to sdr, its just the input
> device API. So until a new API is created there is no benefit from
> a new library in the release.
>
> This also avoids the need for build system changes for a new library
I have no words
_______________________________________________
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:[~2023-07-28 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 22:38 [FFmpeg-devel] [PATCH 1/2] avradio/sdr: Add CQUAM support Michael Niedermayer
2023-07-27 22:38 ` [FFmpeg-devel] [PATCH 2/2] Move sdr within the libavradio repository Michael Niedermayer
2023-07-28 10:39 ` Kieran Kunhya [this message]
2023-08-05 17:56 ` [FFmpeg-devel] [PATCH 1/2] avradio/sdr: Add CQUAM support Michael Niedermayer
2023-08-05 18:26 ` Paul B Mahol
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='CABGuwE=McK8aAw-unz1uiJaNsXaMniPB77jm=rK+DGBsW0s7xA@mail.gmail.com' \
--to=kieran618@googlemail.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