From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org> To: ffmpegagent <ffmpegagent@gmail.com>, "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v6 0/2] ffbuild/commonmak: Fix rebuild check with implicit rule chains Date: Tue, 17 Jun 2025 16:41:38 +0000 Message-ID: <DM8P223MB036562ABBA0EDCAE50628E58BA73A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <pull.80.v6.ffstaging.FFmpeg.1750176111.ffmpegagent@gmail.com> > -----Original Message----- > From: ffmpegagent <ffmpegagent@gmail.com> > Sent: Tuesday, June 17, 2025 6:02 PM > To: ffmpeg-devel@ffmpeg.org > Cc: softworkz <softworkz@hotmail.com> > Subject: [PATCH v6 0/2] ffbuild/commonmak: Fix rebuild check with implicit > rule chains [..] > V4 > == > > * Always keep .ptx files (as suggested by Timo - thanks) Tested all > scenarios: > * .ptx.c and .ptx.gz still get deleted (as intermediates) > * repeated make shows "up-to-date" > * removing a .ptx file does not cause a rebuild (it's still an > intermediate, but an "intermediate to keep") > * but changing a .ptx does (in case of dev/debugging) > * changed .cu files always rebuild of course > > > V5 > == > > * First patch remains unchanged > * Added second patch to clean up and consolidate the rules around > compression > > > V6 > == > > * Rebased > * Confirmed that it also resolves MSVC-CLang compilation > (as reported by Kasper Michalow - thanks!) @Andreas - this slightly conflicts with your WIP patchset. Do you think it makes sense to get this one merged first? It would also need a review, I'm not going to push this without, even though I believe it's the most suitable and straightforward way to get all the issues fixed that it covers (up-to-date check wrt. double-make, log-spam, log prefixes, common.mak sanity and MSVC-CLang build). Thanks, sw _______________________________________________ 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:[~2025-06-17 16:41 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-05-18 2:14 [FFmpeg-devel] [PATCH] " softworkz 2025-05-18 6:30 ` [FFmpeg-devel] [PATCH v2] " softworkz 2025-05-20 19:09 ` softworkz . 2025-05-20 19:36 ` Ramiro Polla 2025-05-20 19:46 ` softworkz . 2025-05-20 20:28 ` Ramiro Polla 2025-05-20 21:13 ` softworkz . 2025-05-20 21:51 ` softworkz . 2025-05-20 23:32 ` [FFmpeg-devel] [PATCH v3] " softworkz 2025-05-23 22:05 ` [FFmpeg-devel] [PATCH v4] " softworkz 2025-05-27 21:41 ` [FFmpeg-devel] [PATCH v5 0/2] " ffmpegagent 2025-05-27 21:41 ` [FFmpeg-devel] [PATCH v5 1/2] " softworkz 2025-05-27 21:41 ` [FFmpeg-devel] [PATCH v5 2/2] ffbuild/commonmak: Consolidate pattern rules for compression softworkz 2025-06-17 16:01 ` [FFmpeg-devel] [PATCH v6 0/2] ffbuild/commonmak: Fix rebuild check with implicit rule chains ffmpegagent 2025-06-17 16:01 ` [FFmpeg-devel] [PATCH v6 1/2] " softworkz 2025-06-17 16:01 ` [FFmpeg-devel] [PATCH v6 2/2] ffbuild/commonmak: Consolidate pattern rules for compression softworkz 2025-06-17 16:41 ` softworkz . [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=DM8P223MB036562ABBA0EDCAE50628E58BA73A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=ffmpegagent@gmail.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