Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC 2/3] ref-manual: Update SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
Date: Tue, 27 Feb 2018 16:47:52 -0600	[thread overview]
Message-ID: <20180227224753.30881-3-JPEWhacker@gmail.com> (raw)
In-Reply-To: <20180227224753.30881-1-JPEWhacker@gmail.com>

Describes the new wildcard syntax in the documentation

Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
 documentation/ref-manual/ref-variables.xml | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 137a556d929..c5db057174b 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -12635,6 +12635,24 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
                     <filename>mplayer2</filename>.
                 </para>
 
+                <para>
+                    The special token <filename>"*"</filename> may be used on
+                    the left hand side of the dependency, which has the special
+                    meaning "all other recipes, except the one on the right hand
+                    side.
+                    For example:
+                    <literallayout class='monospaced'>
+    SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += "*->quilt-native"
+                    </literallayout>
+                </para>
+
+                <para>
+                    In this example, all recipes except
+                    <filename>quilt-native</filename> will ignore task
+                    signatures from the <filename>quilt-native</filename> recipe
+                    when determining their task signatures.
+                </para>
+
                 <para>
                     Use of this variable is one mechanism to remove dependencies
                     that affect task signatures and thus force rebuilds when a
-- 
2.14.3



  parent reply	other threads:[~2018-02-27 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 22:47 [RFC 0/3] Add wildcards to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS Joshua Watt
2018-02-27 22:47 ` [RFC 1/3] sstatesig: Add recipe wildcard Joshua Watt
2018-02-27 22:47 ` Joshua Watt [this message]
2018-02-27 22:47 ` [RFC 3/3] sstatesig: Move hardcoded native tools Joshua Watt
2018-02-28 14:14 ` [RFC 0/3] Add wildcards to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS Richard Purdie
2018-02-28 14:43   ` Joshua Watt

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=20180227224753.30881-3-JPEWhacker@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.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