From: "Leif Lindholm" <leif@nuviainc.com>
To: Bob Feng <bob.c.feng@intel.com>
Cc: devel@edk2.groups.io, Liming Gao <gaoliming@byosoft.com.cn>,
Yuwei Chen <yuwei.chen@intel.com>,
Matthew Carlson <matthewfcarlson@gmail.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [Patch] BaseTools: Fix the ending character for Linux script BuildEnv
Date: Tue, 9 Feb 2021 15:01:18 +0000 [thread overview]
Message-ID: <20210209150118.GJ1664@vanye> (raw)
In-Reply-To: <20210209145808.451-1-bob.c.feng@intel.com>
On Tue, Feb 09, 2021 at 22:58:08 +0800, Bob Feng wrote:
> Signed-off-by: Bob Feng <bob.c.feng@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Yuwei Chen <yuwei.chen@intel.com>
> Cc: Matthew Carlson <matthewfcarlson@gmail.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Leif Lindholm <leif@nuviainc.com>
SMTP strips the intersting aspect, but as long as the end result is a
BuildEnv that has no <CR> characters:
Reviewed-by: Leif Lindholm <leif@nuviainc.com>
> ---
> BaseTools/BuildEnv | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/BaseTools/BuildEnv b/BaseTools/BuildEnv
> index 8d283e10c0..275f4c5901 100755
> --- a/BaseTools/BuildEnv
> +++ b/BaseTools/BuildEnv
> @@ -44,11 +44,11 @@ RestorePreviousConfiguration() {
> break
> fi
> done
> fi
> fi
> -
> +
> PREVIOUS_CONF_FILE=$CONF_PATH/BuildEnv.sh
> if [ -e $PREVIOUS_CONF_FILE ]
> then
> echo Loading previous configuration from $PREVIOUS_CONF_FILE
> . $PREVIOUS_CONF_FILE
> @@ -196,21 +196,21 @@ AddEdkToolsToPath() {
> return 1
> fi
>
> EDK_TOOLS_PATH_BIN=`GetEdkToolsPathBinDirectory`
>
> - # check if the edk2basetools pip package is available
> - if $PYTHON_COMMAND -c "import edk2basetools" &> /dev/null; then
> - # if it is, use the pip version of the wrappers
> - echo "Using Pip Basetools"
> - AddDirToStartOfPath $EDK_TOOLS_PATH/BinPipWrappers/PosixLike
> - else
> - echo "Using EDK2 in-source Basetools"
> - AddDirToStartOfPath $EDK_TOOLS_PATH/BinWrappers/PosixLike
> - fi
> -
> -
> + # check if the edk2basetools pip package is available
> + if $PYTHON_COMMAND -c "import edk2basetools" &> /dev/null; then
> + # if it is, use the pip version of the wrappers
> + echo "Using Pip Basetools"
> + AddDirToStartOfPath $EDK_TOOLS_PATH/BinPipWrappers/PosixLike
> + else
> + echo "Using EDK2 in-source Basetools"
> + AddDirToStartOfPath $EDK_TOOLS_PATH/BinWrappers/PosixLike
> + fi
> +
> +
> AddDirToStartOfPath $EDK_TOOLS_PATH_BIN
>
> }
>
> CopySingleTemplateFile() {
> --
> 2.29.1.windows.1
>
next prev parent reply other threads:[~2021-02-09 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 14:58 [Patch] BaseTools: Fix the ending character for Linux script BuildEnv Bob Feng
2021-02-09 15:01 ` Leif Lindholm [this message]
2021-02-09 15:03 ` Bob Feng
2021-02-10 1:20 ` Michael D Kinney
2021-02-10 1:52 ` Michael D Kinney
2021-02-10 9:54 ` 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=20210209150118.GJ1664@vanye \
--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