[FFmpeg-devel] [PATCH 0/2] Support long file names on Windows
Soft Works
softworkz at hotmail.com
Sun May 15 23:31:48 EEST 2022
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of nil-
> admirari at mailo.com
> Sent: Sunday, May 15, 2022 9:36 PM
> To: ffmpeg-devel at ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 0/2] Support long file names on
> Windows
>
> > I have kept the individual functions separate on purpose, to make it
> easy to
> > compare with the .NET impl. (compilers should inlinie those anyway)
>
> Calling add_extended_prefix without pre-validation results in error,
> since it does check for \\?\, \\.\, or \??\; only it's wrapper
> get_extended_win32_path does.
> And it's not private, it's in the header.
> path_normalize is a do nothing function.
>
> Keeping the comments about where the code originated from may be
> useful.
> Copying the structure of .NET results in problems.
I can squash them together if that would be a common desire.
> These patches are very difficult to review. E.g. stat is not covered:
> https://ffmpeg.org/pipermail/ffmpeg-devel/2022-May/296448.html.
I'll look into stat in a moment.
>
> Parts of FFmpeg still use fopen instead of av_fopen_utf8. Some of
> these uses are
> in examples or tests or inside #ifdef DEBUG blocks.
> Others aren't: dvdsubdec.c:620 uses fopen and it is not covered by
> your
> previous patchset https://ffmpeg.org/pipermail/ffmpeg-devel/2022-
> May/296189.html.
I have left those out by intention because they are pending removal
and are only for debugging.
Thanks again,
softworkz
More information about the ffmpeg-devel
mailing list