From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: softworkz <softworkz@hotmail.com>
Subject: Re: [FFmpeg-devel] [PATCH] fftools/fopen_utf8: support long paths on Windows for fftools
Date: Sun, 19 Jun 2022 00:49:51 +0300 (EEST)
Message-ID: <404d4281-29d4-fed1-c73-6397c015f85e@martin.st> (raw)
In-Reply-To: <pull.36.ffstaging.FFmpeg.1655163773842.ffmpegagent@gmail.com>
On Mon, 13 Jun 2022, softworkz wrote:
> From: softworkz <softworkz@hotmail.com>
>
> Signed-off-by: softworkz <softworkz@hotmail.com>
> ---
> fftools/fopen_utf8: support long paths on Windows for fftools
>
> After Nil's patchset, this is probably the final missing bit.
>
> Signed-off-by: softworkz softworkz@hotmail.com
>
> Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-36%2Fsoftworkz%2Fsubmit_fftools_long_paths-v1
> Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-36/softworkz/submit_fftools_long_paths-v1
> Pull-Request: https://github.com/ffstaging/FFmpeg/pull/36
>
> fftools/fopen_utf8.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fftools/fopen_utf8.h b/fftools/fopen_utf8.h
> index cd18fe8ce1..e5be84179a 100644
> --- a/fftools/fopen_utf8.h
> +++ b/fftools/fopen_utf8.h
> @@ -35,7 +35,7 @@ static inline FILE *fopen_utf8(const char *path_utf8, const char *mode)
> FILE *f;
>
> /* convert UTF-8 to wide chars */
> - if (utf8towchar(path_utf8, &path_w)) /* This sets errno on error. */
> + if (get_extended_win32_path(path_utf8, &path_w)) /* This sets errno on error. */
> return NULL;
> if (!path_w)
> goto fallback;
>
> base-commit: 4d45f5acbd9ab55cd8d29d01843f28315ee27fee
> --
> ffmpeg-codebot
Looks ok, will push soon.
// Martin
_______________________________________________
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".
prev parent reply other threads:[~2022-06-18 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 23:42 softworkz
2022-06-18 21:49 ` Martin Storsjö [this message]
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=404d4281-29d4-fed1-c73-6397c015f85e@martin.st \
--to=martin@martin.st \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=softworkz@hotmail.com \
/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