From: Leif Lindholm <leif.lindholm@linaro.org>
To: Chris Co <Christopher.Co@microsoft.com>, sami.mujawar@arm.com
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Yonghong Zhu <yonghong.zhu@intel.com>,
Liming Gao <liming.gao@intel.com>,
evan.lloyd@arm.com
Subject: Re: [PATCH v1 1/1] BaseTools/Trim: Canonicalize filepaths to fix comparison
Date: Wed, 27 Jun 2018 10:43:32 +0100 [thread overview]
Message-ID: <20180627094332.fh5dt3cabrieyxmt@bivouac.eciton.net> (raw)
In-Reply-To: <20180627035753.49848-2-christopher.co@microsoft.com>
Sami, Evan? I think we need your input/review here.
On Wed, Jun 27, 2018 at 03:58:06AM +0000, Chris Co wrote:
> When using Linaro GCC5+ arm-eabi toolchain on Windows, the generated
> DSDT.iii contains a canonicalized ("\.\" removed and lower case)
> filepath for the preprocessed DSDT.i file in the first line.
> Due to this, when Trim.exe is called to generate DSDT.iiii, future
> filepath comparisons against this canonicalized filepath, which
> should match, actually fail the comparison which results in an
> empty DSDT.iiii.
>
> Issue was first reported to Linaro here:
> https://bugs.linaro.org/show_bug.cgi?id=2909
> where the recommendation was to address the issue in Trim.exe.
>
> This patch canonicalizes and lower cases all file paths encountered
> during trim execution on preprocessed files. Since file paths are
> standarized, the comparison succeeds for files that should match
> regardless of the presence of upper case or "\.\" characters in
> the file path.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Christopher Co <christopher.co@microsoft.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> Cc: Yonghong Zhu <yonghong.zhu@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> ---
> BaseTools/Source/Python/Trim/Trim.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/BaseTools/Source/Python/Trim/Trim.py b/BaseTools/Source/Python/Trim/Trim.py
> index a74075859148..cca4e5c9694a 100644
> --- a/BaseTools/Source/Python/Trim/Trim.py
> +++ b/BaseTools/Source/Python/Trim/Trim.py
> @@ -166,6 +166,8 @@ def TrimPreprocessedFile(Source, Target, ConvertHex, TrimLong):
> if len(MatchList) == 2:
> LineNumber = int(MatchList[0], 0)
> InjectedFile = MatchList[1]
> + InjectedFile = InjectedFile.replace("\\.\\","")
> + InjectedFile = InjectedFile.lower()
> # The first injetcted file must be the preprocessed file itself
> if PreprocessedFile == "":
> PreprocessedFile = InjectedFile
> --
> 2.16.2.gvfs.1.33.gf5370f1
>
next prev parent reply other threads:[~2018-06-27 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 3:58 [PATCH v1 0/1] BaseTools/Trim: Canonicalize filepaths to fix comparison Chris Co
2018-06-27 3:58 ` [PATCH v1 1/1] " Chris Co
2018-06-27 6:59 ` Gao, Liming
2018-06-27 9:43 ` Leif Lindholm [this message]
2018-06-27 11:35 ` Evan Lloyd
2018-06-27 18:13 ` Chris Co
2018-06-27 18:23 ` Chris Co
2018-06-27 20:03 ` Chris Co
2018-06-28 10:35 ` Evan Lloyd
2018-06-28 13:40 ` Gao, Liming
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=20180627094332.fh5dt3cabrieyxmt@bivouac.eciton.net \
--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