From patchwork Thu Nov 17 22:42:47 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Add PATCHRESOLVE to excluded vars for generating sstate-cache Date: Thu, 17 Nov 2011 22:42:47 -0000 From: Matthew McClintock X-Patchwork-Id: 15101 Message-Id: <1321569767-21633-1-git-send-email-msm@freescale.com> To: The method of resolving the patch should not effect the sstate-cache signature. Signed-off-by: Matthew McClintock --- I'm not 100% sure about this one either - should we even generate sstate-cache at all if we have a scenario where we try to resolve a patch? meta/classes/patch.bbclass | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/meta/classes/patch.bbclass b/meta/classes/patch.bbclass index 7622163..5f9765c 100644 --- a/meta/classes/patch.bbclass +++ b/meta/classes/patch.bbclass @@ -138,7 +138,7 @@ python patch_do_patch() { raise bb.build.FuncFailed(str(sys.exc_value)) resolver.Resolve() } -patch_do_patch[vardepsexclude] = "DATE SRCDATE" +patch_do_patch[vardepsexclude] = "DATE SRCDATE PATCHRESOLVE" addtask patch after do_unpack do_patch[dirs] = "${WORKDIR}"