Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "liu.ming50@gmail.com" <liu.ming50@gmail.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2] externalsrc.bbclass: introduce	INHIBIT_SRCTREE_FILE_CHECKSUMES
Date: Tue, 17 Apr 2018 00:34:45 +0000	[thread overview]
Message-ID: <71cdd480b91641c0967948e7db68e82f@XBOX02.axis.com> (raw)
In-Reply-To: <1523924710-21480-1-git-send-email-liu.ming50@gmail.com>

> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> liu.ming50@gmail.com
> Sent: den 17 april 2018 02:25
> To: openembedded-core@lists.openembedded.org
> Cc: Ming Liu <liu.ming50@gmail.com>
> Subject: [OE-core] [PATCH V2] externalsrc.bbclass: introduce INHIBIT_SRCTREE_FILE_CHECKSUMES

Please correct the subject as well.

> From: Ming Liu <liu.ming50@gmail.com>
> 
> It defaults to be '0', but it allows the developers to choose not add
> file-checksums to do_compile for the entire source tree, by setting to
> '1'.
> 
> We need this because we have a huge project with 100G bytes source
> files, and we do not want them to be added to file-checksums variable
> flag.
> 
> Signed-off-by: Ming Liu <liu.ming50@gmail.com>
> ---
>  meta/classes/externalsrc.bbclass | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/externalsrc.bbclass
> b/meta/classes/externalsrc.bbclass
> index c9f5cf7..2b83193 100644
> --- a/meta/classes/externalsrc.bbclass
> +++ b/meta/classes/externalsrc.bbclass
> @@ -26,6 +26,7 @@
> 
>  SRCTREECOVEREDTASKS ?= "do_patch do_unpack do_fetch"
>  EXTERNALSRC_SYMLINKS ?= "oe-workdir:${WORKDIR} oe-logs:${T}"
> +INHIBIT_SRCTREE_FILE_CHECKSUMS ?= "0"
> 
>  python () {
>      externalsrc = d.getVar('EXTERNALSRC')
> @@ -212,7 +213,7 @@ def srctree_hash_files(d, srcdir=None):
>          with open(oe_hash_file, 'w') as fobj:
>              fobj.write(sha1)
>          ret = oe_hash_file + ':True'
> -    else:
> +    elif not d.getVar('INHIBIT_SRCTREE_FILE_CHECKSUMS'):
>          ret = s_dir + '/*:True'
>      return ret
> 
> --
> 2.7.4

//Peter



  reply	other threads:[~2018-04-17  0:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17  0:25 [PATCH V2] externalsrc.bbclass: introduce INHIBIT_SRCTREE_FILE_CHECKSUMES liu.ming50
2018-04-17  0:34 ` Peter Kjellerstedt [this message]
2018-04-17  0:42   ` Ming Liu

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=71cdd480b91641c0967948e7db68e82f@XBOX02.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=liu.ming50@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