public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Feng, Bob C" <bob.c.feng@intel.com>
Cc: dann frazier <dann.frazier@canonical.com>
Subject: Re: [edk2-devel] [Patch 1/1] BaseTools: Fix the lib order in static_library_files.lst
Date: Sun, 29 Sep 2019 03:33:51 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E50CEFA@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190927113523.25424-1-bob.c.feng@intel.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

>-----Original Message-----
>From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
>Bob Feng
>Sent: Friday, September 27, 2019 7:35 PM
>To: devel@edk2.groups.io
>Cc: Gao, Liming <liming.gao@intel.com>; dann frazier
><dann.frazier@canonical.com>; Feng, Bob C <bob.c.feng@intel.com>
>Subject: [edk2-devel] [Patch 1/1] BaseTools: Fix the lib order in
>static_library_files.lst
>
>Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2216
>
>This patch is going to fix the lib order in static_library_files.lst.
>This issue is introduced by commit 673d09a2dd.
>Before 673d09a2dd, build tool apply build rule for the module's library
>firstly and then apply build rule for module itself. Now, build tool
>apply build rule for module self and then for its library. That behavior
>impact the lib order in static_library_files.lst.
>
>This patch is to call module's LibraryAutoGenList function
>explicitly, where the applying build rule action for
>library is triggered.
>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: dann frazier <dann.frazier@canonical.com>
>Signed-off-by: Bob Feng <bob.c.feng@intel.com>
>---
> BaseTools/Source/Python/AutoGen/ModuleAutoGen.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/BaseTools/Source/Python/AutoGen/ModuleAutoGen.py
>b/BaseTools/Source/Python/AutoGen/ModuleAutoGen.py
>index fad5bab0f24d..f0812b6887be 100755
>--- a/BaseTools/Source/Python/AutoGen/ModuleAutoGen.py
>+++ b/BaseTools/Source/Python/AutoGen/ModuleAutoGen.py
>@@ -1841,11 +1841,11 @@ class ModuleAutoGen(AutoGen):
>                 LibraryAutoGen.CreateCodeFile()
>
>         # CanSkip uses timestamps to determine build skipping
>         if self.CanSkip():
>             return
>-
>+        self.LibraryAutoGenList
>         AutoGenList = []
>         IgoredAutoGenList = []
>
>         for File in self.AutoGenFileList:
>             if GenC.Generate(File.Path, self.AutoGenFileList[File], File.IsBinary):
>--
>2.20.1.windows.1
>
>
>


      parent reply	other threads:[~2019-09-29  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 11:35 [Patch 1/1] BaseTools: Fix the lib order in static_library_files.lst Bob Feng
2019-09-27 14:02 ` dann frazier
2019-09-29  3:33 ` Liming Gao [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E50CEFA@SHSMSX104.ccr.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