Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: ffmpegagent <ffmpegagent@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: softworkz <softworkz@hotmail.com>
Subject: [FFmpeg-devel] [PATCH v5 0/2] ffbuild/commonmak: Fix rebuild check with implicit rule chains
Date: Tue, 27 May 2025 21:41:25 +0000
Message-ID: <pull.80.v5.ffstaging.FFmpeg.1748382088.ffmpegagent@gmail.com> (raw)
In-Reply-To: <pull.80.v4.ffstaging.FFmpeg.1748037922309.ffmpegagent@gmail.com>


V2
==

 * Fix MSVC build
   (use the universal command pattern)


V3
==

 * Skip dependency generation by clearing CC_DEPS instead
   (as suggested by Ramiro - thanks!)


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

.

softworkz (2):
  ffbuild/commonmak: Fix rebuild check with implicit rule chains
  ffbuild/commonmak: Consolidate pattern rules for compression

 ffbuild/common.mak | 52 +++++++++++++++++++++++-----------------------
 1 file changed, 26 insertions(+), 26 deletions(-)


base-commit: 4099d53759ce5d9190a339c02b6bb486e2880f66
Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-80%2Fsoftworkz%2Fsubmit_commonmak-v5
Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-80/softworkz/submit_commonmak-v5
Pull-Request: https://github.com/ffstaging/FFmpeg/pull/80

Range-diff vs v4:

 1:  20c2fb65ed = 1:  20c2fb65ed ffbuild/commonmak: Fix rebuild check with implicit rule chains
 -:  ---------- > 2:  9ff1856142 ffbuild/commonmak: Consolidate pattern rules for compression

-- 
ffmpeg-codebot
_______________________________________________
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:[~2025-05-27 21: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       ` ffmpegagent [this message]
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           ` [FFmpeg-devel] [PATCH v6 0/2] ffbuild/commonmak: Fix rebuild check with implicit rule chains softworkz .

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=pull.80.v5.ffstaging.FFmpeg.1748382088.ffmpegagent@gmail.com \
    --to=ffmpegagent@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=softworkz@hotmail.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