From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-infra: add <pkg>-extract and <pkg>-patch targets to OVERRIDE support
Date: Fri, 7 Dec 2012 00:16:00 +0100 [thread overview]
Message-ID: <1354835760-9357-1-git-send-email-arnout@mind.be> (raw)
From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
The legal-info target (and possibly others as well) depends on
<pkg>-extract to make sure the license file is available. However,
when <PKG>_OVERRIDE_SRCDIR is active, the <pkg>-extract target
doesn't exist.
To solve this, we add <pkg>-extract which depends on <pkg>-rsync.
While we're at it, we do the same for <pkg>-patch. That avoids the
same problem in the future if something starts depending on
<pkg>-patch.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: Luca Ceresoli <luca@lucaceresoli.net>
---
v2: As ThomasP suggested, don't remove <pkg>-rsync.
---
package/pkg-generic.mk | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/pkg-generic.mk b/package/pkg-generic.mk
index 6fcd359..13c1d83 100644
--- a/package/pkg-generic.mk
+++ b/package/pkg-generic.mk
@@ -390,6 +390,9 @@ $(1)-configure: $(1)-depends \
$(1)-depends: $(1)-rsync $$($(2)_DEPENDENCIES)
+$(1)-patch: $(1)-rsync
+$(1)-extract: $(1)-rsync
+
$(1)-rsync: $$($(2)_TARGET_RSYNC)
$(1)-source: $$($(2)_TARGET_RSYNC_SOURCE)
--
1.7.10.4
next reply other threads:[~2012-12-06 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 23:16 Arnout Vandecappelle [this message]
2012-12-07 1:14 ` [Buildroot] [PATCH] pkg-infra: add <pkg>-extract and <pkg>-patch targets to OVERRIDE support Peter Korsgaard
2012-12-07 10:32 ` Stephan Hoffmann
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=1354835760-9357-1-git-send-email-arnout@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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