Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 0/8] add fd protocol
Date: Fri, 13 Jan 2023 20:12:54 +0200
Message-ID: <209205422.TKlkgKsTHV@basile.remlab.net> (raw)
In-Reply-To: <tencent_833FEB566D9DECE0B05B00353581FC346709@qq.com>

Le perjantaina 13. tammikuuta 2023, 5.37.36 EET zhilizhao(赵志立) a écrit :
> > On Jan 13, 2023, at 03:13, Rémi Denis-Courmont <remi@remlab.net> wrote:
> > 
> > Le keskiviikkona 11. tammikuuta 2023, 10.52.08 EET Paul B Mahol a écrit :
> >>> Sorry for the break, I’m trying to figure out how to make it compatible
> >>> with Windows.
> >> 
> >> Is this even portable?
> > 
> > If you build FFmpeg correctly, so that all the FFmpeg libraries and the
> > application code share the same instance of the same CRT, yes. That is to
> > say, you can use POSIX-style file descriptors.
> > 
> > Whether it is of any practical usefulness is more questionable, as those
> > file descriptors are not passed from parent to child processes
> 
> When an app requests a media file, Android system provides it as a file
> descriptor over IPC for security. Users may find other usecases.

I'm not quite clear how that is relevant to Windows, TBH.

-- 
Rémi Denis-Courmont
http://www.remlab.net/



_______________________________________________
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".

  reply	other threads:[~2023-01-13 18:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <34df4f8e-0c8b-4199-8a4b-5669078b4a25@EX-SZ069.tencent.com>
2023-01-09  3:17 ` "zhilizhao(赵志立)"
2023-01-11  3:18   ` "zhilizhao(赵志立)"
2023-01-11  7:53     ` Xiang, Haihao
2023-01-11  8:31       ` "zhilizhao(赵志立)"
2023-01-11  8:52         ` Paul B Mahol
2023-01-11  9:10           ` "zhilizhao(赵志立)"
2023-01-12  1:26             ` Xiang, Haihao
2023-01-12  7:29               ` "zhilizhao(赵志立)"
2023-01-12 19:13           ` Rémi Denis-Courmont
2023-01-13  3:37             ` "zhilizhao(赵志立)"
2023-01-13 18:12               ` Rémi Denis-Courmont [this message]
2023-01-11  9:02         ` "zhilizhao(赵志立)"
2022-12-14 17:10 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=209205422.TKlkgKsTHV@basile.remlab.net \
    --to=remi@remlab.net \
    --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