From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] lavc: move bitstream filters into bsf/ subdir Date: Fri, 26 Jan 2024 13:22:06 -0300 Message-ID: <dbd0ae02-26f1-4ef8-9b1c-d8bf2eb95569@gmail.com> (raw) In-Reply-To: <170628585789.8914.11774088021293158816@lain.khirnov.net> On 1/26/2024 1:17 PM, Anton Khirnov wrote: > Quoting James Almer (2024-01-26 17:09:32) >> On 1/26/2024 9:17 AM, Anton Khirnov wrote: >>> Quoting Lynne (2024-01-26 13:11:33) >>>> Jan 26, 2024, 11:40 by anton@khirnov.net: >>>> >>>>> --- >>>>> libavcodec/Makefile | 49 +--------------- >>>>> libavcodec/bsf/Makefile | 56 +++++++++++++++++++ >>>>> >>>> >>>> Is that the general direction we want to take? >>>> I don't mind it, but I'm wondering if I should do this for what I care about? >>> >>> I'd say yes for things with >~ 10 files. libavcodec/ got way too large. >> >> Is your idea something like.. >> >> libavcodec/bsf >> libavcodec/common >> libavcodec/decoder >> libavcodec/encoder >> libavcodec/parser >> >> And then subfolders within those for big modules like h264, hevc, vvc, >> mpeg2, vp9, etc? > > No, that strikes me as overkill. A subdir for bsfs, a subdir for every > codec/group of codecs/subsystem. I don't think it's overkill. It separates modules per type, so it's easy to find a parser that right now is mixed between all the decoder related files. > >> And like Andreas mentioned, the arch subfolders need to be considered >> for this. > > Why? I mean, where do you want them? inside the decoder/encoder subfolders (thus splitting them), or outside as they are right now? _______________________________________________ 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".
next prev parent reply other threads:[~2024-01-26 16:22 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-26 10:39 Anton Khirnov 2024-01-26 12:11 ` Lynne 2024-01-26 12:17 ` Zhao Zhili 2024-01-26 12:17 ` Anton Khirnov 2024-01-26 16:09 ` James Almer 2024-01-26 16:17 ` Anton Khirnov 2024-01-26 16:22 ` James Almer [this message] 2024-01-26 16:24 ` Anton Khirnov 2024-01-26 12:35 ` Andreas Rheinhardt 2024-01-26 16:22 ` Anton Khirnov 2024-01-28 17:49 ` Anton Khirnov 2024-01-29 9:57 ` Andreas Rheinhardt 2024-01-29 10:21 ` Anton Khirnov 2024-01-29 10:55 ` Andreas Rheinhardt 2024-01-29 11:07 ` Anton Khirnov 2024-01-29 11:15 ` Anton Khirnov 2024-01-29 11:29 ` Andreas Rheinhardt
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=dbd0ae02-26f1-4ef8-9b1c-d8bf2eb95569@gmail.com \ --to=jamrial@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