Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Mark Gaiser <markg85@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v1] avformat/ipfsgateway: define PATH_MAX
Date: Thu, 14 Apr 2022 14:46:58 +0200
Message-ID: <CAPd6JnF37cDsuK=CO_u6u+xEJvWWc8VvE582CDwGxJfRJBPaKQ@mail.gmail.com> (raw)
In-Reply-To: <fba7e841-ced3-103c-1d26-f1d14be09de9@martin.st>

On Thu, Apr 14, 2022 at 10:25 AM Martin Storsjö <martin@martin.st> wrote:

> On Wed, 13 Apr 2022, Mark Gaiser wrote:
>
> > On Wed, Apr 13, 2022 at 5:21 PM Mark Gaiser <markg85@gmail.com> wrote:
> >
> >> PATH_MAX is posix. Some compilers (MSVC) don't define this
> >> thus failing to compile the ipfsgateway file.
> >> Defining it fixes the compile.
> >>
> >> Signed-off-by: Mark Gaiser <markg85@gmail.com>
> >> ---
> >>  libavformat/ipfsgateway.c | 6 ++++++
> >>  1 file changed, 6 insertions(+)
> >>
> >> diff --git a/libavformat/ipfsgateway.c b/libavformat/ipfsgateway.c
> >> index ed37e552dd..9b0d3dea59 100644
> >> --- a/libavformat/ipfsgateway.c
> >> +++ b/libavformat/ipfsgateway.c
> >> @@ -25,6 +25,12 @@
> >>  #include "os_support.h"
> >>  #include "url.h"
> >>
> >> +// Define the posix PATH_MAX if not there already.
> >> +// This fixes a compile issue for MSVC.
> >> +#ifndef PATH_MAX
> >> +#define PATH_MAX 4096
> >> +#endif
> >> +
> >>  typedef struct IPFSGatewayContext {
> >>      AVClass *class;
> >>      URLContext *inner;
> >> --
> >> 2.35.1
> >
> > I did verify the size of PATH_MAX. On my pc (arch with GCC compiler)
> > this value is defined as 4096. That seems enough to me. Another way to
> > fix this is to add it in os_support.h. I didn't add it there because
> > ipfsgateway.c is currently the only cross-platform code that makes use
> > of this.
> >
> > Lastly, I don't have an MSVC compiler and windows to test this on.
> > I hope someone else in that setup can verify that this does indeed fix
> the
> > ffmpeg master build?
>
> This looks like a reasonable fix to at least make things build correctly
> again (and it does fix the issue).
>
> FWIW, the corresponding Windows define is MAX_PATH, which usually is 260,
> so setting it to 4096 here is probably more than enough if a hardcoded
> value is needed.
>
> // Martin
>

Glad it works! Thank you for testing.

I don't have commit/merge powers so I leave that in the capable hands of
those that can.

>
> _______________________________________________
> 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".
>
_______________________________________________
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:[~2022-04-14 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 15:21 Mark Gaiser
2022-04-13 15:27 ` Mark Gaiser
2022-04-14  8:25   ` Martin Storsjö
2022-04-14 12:46     ` Mark Gaiser [this message]
2022-04-14 13:41       ` Martin Storsjö
2022-04-14 13:48         ` Mark Gaiser

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='CAPd6JnF37cDsuK=CO_u6u+xEJvWWc8VvE582CDwGxJfRJBPaKQ@mail.gmail.com' \
    --to=markg85@gmail.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