public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: "Carsey, Jaben" <jaben.carsey@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH v1 1/1] BaseTools/GenFds: Verify binaries all the time
Date: Thu, 6 Sep 2018 18:41:55 +0000	[thread overview]
Message-ID: <CB6E33457884FA40993F35157061515CA4132359@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <5ef06f7bf6d4df68579049c0d233c16d7867086a.1536258666.git.jaben.carsey@intel.com>

I have found a related issue.  Please ignore this patch.

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Jaben Carsey
> Sent: Thursday, September 06, 2018 11:31 AM
> To: edk2-devel@lists.01.org
> Cc: Gao, Liming <liming.gao@intel.com>
> Subject: [edk2] [PATCH v1 1/1] BaseTools/GenFds: Verify binaries all the time
> 
> Currently, Basetools only verifies Binary file list existance for default ARCH,
> but it should verify for a specified ARCH the same.
> Also, dont save the list to a unused variable.
> 
> Cc: Yonghong Zhu <yonghong.zhu@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Jaben Carsey <jaben.carsey@intel.com>
> ---
>  BaseTools/Source/Python/GenFds/AprioriSection.py | 10 ++++------
>  1 file changed, 4 insertions(+), 6 deletions(-)
> 
> diff --git a/BaseTools/Source/Python/GenFds/AprioriSection.py
> b/BaseTools/Source/Python/GenFds/AprioriSection.py
> index 7196f7f2c753..70aa150799a7 100644
> --- a/BaseTools/Source/Python/GenFds/AprioriSection.py
> +++ b/BaseTools/Source/Python/GenFds/AprioriSection.py
> @@ -89,12 +89,10 @@ class AprioriSection (AprioriSectionClassObject):
>                      Inf =
> GenFdsGlobalVariable.WorkSpace.BuildObject[PathClass(InfFileName,
> GenFdsGlobalVariable.WorkSpaceDir), TAB_COMMON,
> GenFdsGlobalVariable.TargetName, GenFdsGlobalVariable.ToolChainTag]
>                      Guid = Inf.Guid
> 
> -                    self.BinFileList = Inf.Module.Binaries
> -                    if self.BinFileList == []:
> -                        EdkLogger.error("GenFds", RESOURCE_NOT_AVAILABLE,
> -                                        "INF %s not found in build ARCH %s!" \
> -                                        % (InfFileName, GenFdsGlobalVariable.ArchList))
> -
> +                if not Inf.Module.Binaries:
> +                    EdkLoggerError("GenFds", RESOURCE_NOT_AVAILABLE,
> +                                    "INF %s not found in build ARCH %s!" \
> +                                    % (InfFileName, GenFdsGlobalVariable.ArchList))
> 
>              GuidPart = Guid.split('-')
>              Buffer.write(pack('I', long(GuidPart[0], 16)))
> --
> 2.16.2.windows.1
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2018-09-06 18:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1536258666.git.jaben.carsey@intel.com>
2018-09-06 18:31 ` [PATCH v1 1/1] BaseTools/GenFds: Verify binaries all the time Jaben Carsey
2018-09-06 18:41   ` Carsey, Jaben [this message]

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-list 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=CB6E33457884FA40993F35157061515CA4132359@FMSMSX103.amr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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