Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jaewon Lee <JAEWON@xilinx.com>
Cc: Bruce Ashfield <brucea@xilinx.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [master][PATCH] Introduce mechanism to keep nativesdk* sstate in esdk
Date: Wed, 18 Sep 2019 10:05:09 +1200	[thread overview]
Message-ID: <2420065.Evh0tLMQLu@linux.fritz.box> (raw)
In-Reply-To: <BYAPR02MB5816F67E4B32AB35B425D15DAFA20@BYAPR02MB5816.namprd02.prod.outlook.com>

Hi Jaewon

Richard was waiting for me to review this - unfortunately another one that fell between the cracks - sorry about that.

On Friday, 30 August 2019 5:13:39 AM NZST Jaewon Lee wrote:
> > -----Original Message-----
> > From: Jaewon Lee <jaewon.lee@xilinx.com>
> > Sent: Monday, April 1, 2019 5:07 PM
> > To: openembedded-core@lists.openembedded.org; Alejandro Enedino
> > Hernandez Samaniego <alejandr@xilinx.com>; Manjukumar Harthikote
> > Matha <MANJUKUM@xilinx.com>; Bruce Ashfield <brucea@xilinx.com>
> > Cc: Jaewon Lee <JAEWON@xilinx.com>
> > Subject: [oe-core][master][PATCH] Introduce mechanism to keep nativesdk*
> > sstate in esdk
> > 
> > Using SDK_INCLUDE_NATIVESDK flag to toggle inclusion of all nativesdk*
> > sstate into esdk Currently locked-sigs.inc is generated during
> > do_sdk_depends which doesn't pull in nativesdk packages. Generating
> > another locked-sigs.inc in do_populate_sdk_ext and pruning it to only
> > nativesdk* packages by using a modified version of the already existing
> > function prune_locked_sigs and merging it with the current locked-sigs.inc
> > Also adding SDK_INCLUDE_NATIVESDK tasklistfn to the logic surrounding
> > setting tasklist file to not prune esdk sstate during creation
> > 
> > Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>

The commit message doesn't actually explain why you are adding this functionality. You explained it elsewhere (bug 13261) but it needs to be in here. I would also recommend adding a "Fixes [YOCTO #13261]" at the end so there's a reference back to the bug as well.

> > @@ -414,7 +433,7 @@ python copy_buildsystem () {
> > 
> >      sdk_include_toolchain = (d.getVar('SDK_INCLUDE_TOOLCHAIN') == '1')
> >      sdk_ext_type = d.getVar('SDK_EXT_TYPE')
> > -    if sdk_ext_type != 'minimal' or sdk_include_toolchain or derivative:
> > +    if (sdk_ext_type != 'minimal' or sdk_include_toolchain or derivative) and not sdk_include_nativesdk:
> >          # Create the filtered task list used to generate the sstate cache shipped with the SDK
> >          tasklistfn = d.getVar('WORKDIR') + '/tasklist.txt'
> >          create_filtered_tasklist(d, baseoutpath, tasklistfn, conf_initpath) @@ -

This logic change looks a bit odd. Are you sure this is correct?

Thanks
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre




  parent reply	other threads:[~2019-09-17 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  0:06 [master][PATCH] Introduce mechanism to keep nativesdk* sstate in esdk Jaewon Lee
2019-08-29 17:13 ` Jaewon Lee
2019-09-05  5:46   ` Manjukumar Harthikote Matha
2019-09-17 22:05   ` Paul Eggleton [this message]
2019-09-17 23:35     ` Jaewon Lee

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=2420065.Evh0tLMQLu@linux.fritz.box \
    --to=paul.eggleton@linux.intel.com \
    --cc=JAEWON@xilinx.com \
    --cc=brucea@xilinx.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