From: Mark Gaiser <markg85@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v13 1/1] avformat: Add IPFS protocol support. Date: Wed, 13 Apr 2022 17:13:49 +0200 Message-ID: <CAPd6JnH5JeA0r=uDwJ__AjOOajuOsK_wY6bgARXMw6MXDtnyZA@mail.gmail.com> (raw) In-Reply-To: <CA+anqdw6ZhNPrdCtBChUcZ8v6aq4nw2d+PSnm8EGDhfSBwFXBw@mail.gmail.com> On Wed, Apr 13, 2022 at 4:45 PM Hendrik Leppkes <h.leppkes@gmail.com> wrote: > On Wed, Apr 13, 2022 at 3:14 PM Mark Gaiser <markg85@gmail.com> wrote: > > > > On Wed, Apr 13, 2022 at 2:28 PM Andreas Rheinhardt < > > andreas.rheinhardt@outlook.com> wrote: > > > > > Mark Gaiser: > > > > On Wed, Apr 13, 2022 at 1:10 AM James Almer <jamrial@gmail.com> > wrote: > > > > > > > >> > > > >> > > > >> On 4/12/2022 3:02 PM, Michael Niedermayer wrote: > > > >>> On Sun, Apr 10, 2022 at 04:41:27PM +0200, Michael Niedermayer > wrote: > > > >>>> On Wed, Apr 06, 2022 at 02:00:56PM +0200, Mark Gaiser wrote: > > > >>>> [...] > > > >>>> > > > >>>>> + if (stat_ret < 0) { > > > >>>> > > > >>>>> + av_log(h, AV_LOG_INFO, "Unable to find IPFS folder. > We > > > >> tried:\n"); > > > >>>>> + av_log(h, AV_LOG_INFO, "- $IPFS_PATH, which was > > > >> empty.\n"); > > > >>>>> + av_log(h, AV_LOG_INFO, "- $HOME/.ipfs (full uri: %s) > > > >> which doesn't exist.\n", ipfs_full_data_folder); > > > >>>> > > > >>>> The 3 av_log() can also be combined > > > >>>> > > > >>>> If nothing else is found then ill change that myself and apply in > a > > > day > > > >> or 2 > > > >>> > > > >>> applied > > > >>> > > > >>> thx > > > >> > > > >> This broke msvc > > > >> > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(36): > > > >> error C2065: 'PATH_MAX': undeclared identifier > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(36): > > > >> error C2057: expected constant expression > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(46): > > > >> error C2065: 'PATH_MAX': undeclared identifier > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(46): > > > >> error C2057: expected constant expression > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(46): > > > >> error C2466: cannot allocate an array of constant size 0 > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(46): > > > >> error C2133: 'ipfs_full_data_folder': unknown size > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(47): > > > >> error C2065: 'PATH_MAX': undeclared identifier > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(47): > > > >> error C2057: expected constant expression > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(47): > > > >> error C2466: cannot allocate an array of constant size 0 > > > >>> > C:/Dev/ffmpeg/fate/x86_32-msvc-MD/src/libavformat/ipfsgateway.c(47): > > > >> error C2133: 'ipfs_gateway_file': unknown size > > > >> > > > >> PATH_MAX seems to be POSIX only. > > > >> > > > > > > > > Seriously? > > > > > > > > Shouldn't that define work on windows too? > > > > > > For "that define" to work that define needs to exist. Windows has > > > MAX_PATH, but it is pretty small (260). > > > > > > > And why didn't patchwork catch this? > > > > > > > > > > Because there is no MSVC patchwork box. > > > > > > > What is the intended define to use for this? > > > > Note that it used to be a fixed number in the code itself (4096?) > but I > > > > changed it to PATH_MAX as per review suggestions.... > > > > > > Then how about just adding > > > #ifndef MAX_PATH > > > #define MAX_PATH 4096 > > > #endif > > > or something like that. > > > > > > > I'm fine with that but given past feedback I'll wait a little longer for > a > > 2nd opinion too. > > > > master is currently broken, waiting is a luxury for another time. > Fine. Patch incoming. > - Hendrik > _______________________________________________ > 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".
prev parent reply other threads:[~2022-04-13 15:14 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-06 12:00 [FFmpeg-devel] [PATCH v13 0/1] " Mark Gaiser 2022-04-06 12:00 ` [FFmpeg-devel] [PATCH v13 1/1] avformat: " Mark Gaiser 2022-04-07 22:01 ` Mark Gaiser 2022-04-10 14:41 ` Michael Niedermayer 2022-04-11 13:46 ` Mark Gaiser 2022-04-12 18:02 ` Michael Niedermayer 2022-04-12 18:43 ` Mark Gaiser 2022-04-12 23:09 ` James Almer 2022-04-12 23:23 ` Mark Gaiser 2022-04-13 12:28 ` Andreas Rheinhardt 2022-04-13 13:14 ` Mark Gaiser 2022-04-13 14:45 ` Hendrik Leppkes 2022-04-13 15:13 ` Mark Gaiser [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='CAPd6JnH5JeA0r=uDwJ__AjOOajuOsK_wY6bgARXMw6MXDtnyZA@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