From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/file: add fd protocol
Date: Thu, 8 Dec 2022 16:28:30 +0100
Message-ID: <GV1P250MB0737B6EF6AE9D01DC99A6E6E8F1D9@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <63CE0B62-1256-4D18-9166-B5ECFFAB2430@gmail.com>
Marvin Scholz:
>
>
> On 8 Dec 2022, at 16:11, Zhao Zhili wrote:
>
>> On Mon, 2022-12-05 at 10:51 +0800, zhilizhao(赵志立) wrote:
>>>> On Nov 19, 2022, at 02:48, Zhao Zhili <quinkblack@foxmail.com>
>>>> wrote:
>>>>
>>>> From: Zhao Zhili <zhilizhao@tencent.com>
>>>>
>>>> Unlike the pipe protocol, fd protocol has seek support if it
>>>> corresponding to a regular file.
>>>> ---
>>>> Sometimes it's the only way to access files via file descriptor,
>>>> e.g.,
>>>> requesting a shared file on Android:
>>>> https://developer.android.com/training/secure-file-sharing/request-file
>>>>
>>>> doc/protocols.texi | 24 +++++++++++++++++++
>>>> libavformat/Makefile | 1 +
>>>> libavformat/file.c | 51
>>>> +++++++++++++++++++++++++++++++++++++++++
>>>> libavformat/protocols.c | 1 +
>>>> libavformat/version.h | 4 ++--
>>>> 5 files changed, 79 insertions(+), 2 deletions(-)
>>>>
>>>>
>>>
>>> Ping for review.
>>>
>>
>> Will apply tomorrow unless there are objections.
>>
>
> Maybe I overlooked something but where does the CONFIG_FD_PROTOCOL
> define comes from?
>
It is autogenerated by configure due to the entry in lavf/protocols.c
(and this change will trigger a request to rerun configure when compiling).
(I haven't looked at the patch at all.)
- Andreas
_______________________________________________
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:[~2022-12-08 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 18:48 Zhao Zhili
2022-12-05 2:51 ` "zhilizhao(赵志立)"
2022-12-08 15:11 ` Zhao Zhili
2022-12-08 15:16 ` Marvin Scholz
2022-12-08 15:28 ` Andreas Rheinhardt [this message]
2022-12-08 16:16 ` Zhao Zhili
2022-12-12 16:31 ` Rémi Denis-Courmont
2022-12-12 17:23 ` Zhao Zhili
2022-12-13 16:27 ` Rémi Denis-Courmont
2022-12-09 14:31 ` Anton Khirnov
2022-12-10 13:45 ` Zhao Zhili
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=GV1P250MB0737B6EF6AE9D01DC99A6E6E8F1D9@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
--to=andreas.rheinhardt@outlook.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