From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] lavc: move bitstream filters into bsf/ subdir Date: Mon, 29 Jan 2024 12:07:05 +0100 Message-ID: <170652642550.8914.5776548339039666051@lain.khirnov.net> (raw) In-Reply-To: <AS8P250MB07440BD5C71E004FD7E24ABB8F7E2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> Quoting Andreas Rheinhardt (2024-01-29 11:55:19) > Anton Khirnov: > > Quoting Andreas Rheinhardt (2024-01-29 10:57:19) > >> Anton Khirnov: > >>> +# add libavcodec/ to include path for bsfs > >>> +$(addprefix libavcodec/, $(sort $(filter bsf/%,$(OBJS_BSF-yes)))): CPPFLAGS += -I$(SRC_PATH)/libavcodec/ > >> > >> 1. Why sort? > > > > To get rid of duplicates, otherwise the flags can be added multiple > > times. > > > > Why not just use libavcodec/bsf/%.o: CPPFLAGS += -I$(SRC_PATH)/libavcodec/ Sure, it just didn't occur to me. > I was actually proposing that the dependencies for stuff in libavcodec/ > stays in libavcodec/Makefile. Okay, then I would appreciate it if you were more explicit about how you want things changed in the future, it would save time. > PS: Why don't you move e.g. bsf_internal.h as well as bsf.c itself? Because I only wanted to move the bitstream filters themselves in this patch. I have no strong feelings about those two files moving under bsf/ or not. > And where has this actually been discussed for there to be > "overwhelming" consensus for it? As I remember it, various people have complained about the number of files in libavcodec/* for years - on IRC, ML, developer meetings, etc. I don'recall anyone ever being against it. -- Anton Khirnov _______________________________________________ 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-29 11:07 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 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 [this message] 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=170652642550.8914.5776548339039666051@lain.khirnov.net \ --to=anton@khirnov.net \ --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