public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Bob Feng <bob.c.feng@intel.com>, Andrew Fish <afish@apple.com>,
	Leif Lindholm <leif@nuviainc.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <liming.gao@intel.com>
Cc: devel@edk2.groups.io, Pierre Gondois <pierre.gondois@arm.com>
Subject: Re: [Patch 1/1][edk2-stable202002]BaseTools: Fixed a regression issue in Makefile for incremental build
Date: Thu, 27 Feb 2020 13:43:29 +0100	[thread overview]
Message-ID: <e4533aee-a86a-5e5a-eec9-7d5311161185@redhat.com> (raw)
In-Reply-To: <ec4ce7a0-5245-c15b-0420-665231515ecf@redhat.com>

On 02/27/20 13:39, Laszlo Ersek wrote:
> On 02/27/20 10:47, Bob Feng wrote:
>> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2563
>>
>> This patch is to fix a increametal build regression bug 
>> which happen when using nmake. That's introduced by 818283de3f6d.
>>
>> If there is white space before !INCLUDE instruction, nmake will not
>> process it. Source code's dependent header files are listed in
>> ${deps_file} file, if it's not included successfully, nmake will
>> not detect the change of those header file.
>>
>> This patch has been verified in Windows with VS2015 and Linux with GCC5.
>> The header file add/modify/delete can trig the incremental build with this fix.
>> There is no impact on the clean build.
>>
>> Cc: Andrew Fish <afish@apple.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Cc: Leif Lindholm <leif@nuviainc.com>
>> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>> Cc: Pierre Gondois <pierre.gondois@arm.com>
>> Signed-off-by: Bob Feng <bob.c.feng@intel.com>
>> Reviewed-by: Liming Gao <liming.gao@intel.com>
>> Tested-by: Liming Gao <liming.gao@intel.com>
>> ---
>>  .../Source/Python/AutoGen/IncludesAutoGen.py     | 16 ++++++++--------
>>  1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/BaseTools/Source/Python/AutoGen/IncludesAutoGen.py b/BaseTools/Source/Python/AutoGen/IncludesAutoGen.py
>> index 0a6314266f45..720d93395aaf 100644
>> --- a/BaseTools/Source/Python/AutoGen/IncludesAutoGen.py
>> +++ b/BaseTools/Source/Python/AutoGen/IncludesAutoGen.py
>> @@ -50,21 +50,21 @@ class IncludesAutoGen():
>>          MakePath = self.module_autogen.BuildOption.get('MAKE', {}).get('PATH')
>>          if not MakePath:
>>              EdkLogger.error("build", PARAMETER_MISSING, Message="No Make path available.")
>>          elif "nmake" in MakePath:
>>              _INCLUDE_DEPS_TEMPLATE = TemplateString('''
>> -        ${BEGIN}
>> -        !IF EXIST(${deps_file})
>> -        !INCLUDE ${deps_file}
>> -        !ENDIF
>> -        ${END}
>> +${BEGIN}
>> +!IF EXIST(${deps_file})
>> +!INCLUDE ${deps_file}
>> +!ENDIF
>> +${END}
>>                 ''')
>>          else:
>>              _INCLUDE_DEPS_TEMPLATE = TemplateString('''
>> -        ${BEGIN}
>> -        -include ${deps_file}
>> -        ${END}
>> +${BEGIN}
>> +-include ${deps_file}
>> +${END}
>>                 ''')
>>  
>>          try:
>>              deps_include_str = _INCLUDE_DEPS_TEMPLATE.Replace(deps_file)
>>          except Exception as e:
>>
> 
> (1) I agree this should go into edk2-stable202002.
> 
> Acked-by: Laszlo Ersek <lersek@redhat.com>

Before I forget: please update the subject line of this patch to
something that actually carries information. For example:

  BaseTools: remove invalid leading space in nmake rules/directives

I'm not familiar with NMAKE, so maybe "rules" and "directives" aren't
the right terms. Still, the subject should name both NMAKE and leading
space (or whitespace at least).

Laszlo


  reply	other threads:[~2020-02-27 12:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27  9:47 [Patch 1/1][edk2-stable202002]BaseTools: Fixed a regression issue in Makefile for incremental build Bob Feng
2020-02-27 12:39 ` Laszlo Ersek
2020-02-27 12:43   ` Laszlo Ersek [this message]
2020-02-27 14:12   ` [edk2-devel] " Liming Gao
2020-02-27 15:53   ` Bob Feng
2020-02-27 17:17     ` Laszlo Ersek
2020-02-28  1:34       ` Bob Feng

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=e4533aee-a86a-5e5a-eec9-7d5311161185@redhat.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