From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 3/3] libtraceevent: Keep build_install file around
Date: Tue, 15 Dec 2020 23:36:40 -0500 [thread overview]
Message-ID: <20201216043717.176014003@goodmis.org> (raw)
In-Reply-To: 20201216043637.453360298@goodmis.org
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
Instead of rebuilding the build_install files every time the uninstall is
created, make it depend on the prefix, as if the prefix is the same, then
the uninstall should be the same.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index f795e05d22a7..f96232b99e40 100644
--- a/Makefile
+++ b/Makefile
@@ -319,7 +319,7 @@ define build_uninstall_script
$(Q)$(RM) -rf $(BUILD_OUTPUT)/tmp_build
endef
-build_uninstall:
+build_uninstall: $(BUILD_PREFIX)
$(call build_uninstall_script,install,uninstall)
$(BUILD_OUTPUT)/build_uninstall: build_uninstall
@@ -332,7 +332,6 @@ endef
uninstall: $(BUILD_OUTPUT)/build_uninstall
@$(foreach file,$(shell cat $(BUILD_OUTPUT)/build_uninstall),$(call uninstall_file,$(file)))
- $(Q)$(RM) $<
PHONY += doc
doc:
--
2.29.2
prev parent reply other threads:[~2020-12-16 4:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 4:36 [PATCH 0/3] libtraceevent: Add uninstall and fix build dependency of libtraceevent.pc Steven Rostedt
2020-12-16 4:36 ` [PATCH 1/3] libtraceevent: Add a way to uninstall Steven Rostedt
2020-12-16 4:36 ` [PATCH 2/3] libtraceevent: Update libtraceevent.pc if prefix is different Steven Rostedt
2020-12-16 4:36 ` Steven Rostedt [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=20201216043717.176014003@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).