From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [Patch] BaseTools/Tests: Update GNUmakefile to use python3 variable
Date: Sat, 13 Oct 2018 16:53:21 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D5213F5B7@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CAKv+Gu9aiUSzho8KKOD08wzupCy0weTu15cd3F0KqyYF7fW_yg@mail.gmail.com>
Hi Ard,
Thanks. I pushed this patch since it is critical block issue.
Version SHA-1: 678f85131238622e576705117e299d81cff755c9
Best Regards,
Zhu Yonghong
-----Original Message-----
From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
Sent: Sunday, October 14, 2018 12:44 AM
To: Zhu, Yonghong <yonghong.zhu@intel.com>
Cc: edk2-devel@lists.01.org; Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [Patch] BaseTools/Tests: Update GNUmakefile to use python3 variable
On 13 October 2018 at 18:40, Yonghong Zhu <yonghong.zhu@intel.com> wrote:
> Cover the case use do make -C BaseTools before run the .edksetup.sh
> file.
>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> BaseTools/Tests/GNUmakefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/BaseTools/Tests/GNUmakefile b/BaseTools/Tests/GNUmakefile
> index af334a8a..536f0b7 100644
> --- a/BaseTools/Tests/GNUmakefile
> +++ b/BaseTools/Tests/GNUmakefile
> @@ -12,10 +12,10 @@
> #
>
> all: test
>
> test:
> - @if command -v $(PYTHON3) >/dev/null 2>&1; then $(PYTHON3) RunTests.py; else python RunTests.py; fi
> + @if command -v python3 >/dev/null 2>&1; then python3
> + RunTests.py; else echo "Error: Please install a python 3 tool!"; fi
>
> clean:
> find . -name '*.pyc' -exec rm '{}' ';'
>
> --
> 2.6.1.windows.1
>
next prev parent reply other threads:[~2018-10-13 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 16:40 [Patch] BaseTools/Tests: Update GNUmakefile to use python3 variable Yonghong Zhu
2018-10-13 16:43 ` Ard Biesheuvel
2018-10-13 16:53 ` Zhu, Yonghong [this message]
2018-10-13 20:40 ` Leif Lindholm
2018-10-14 9:03 ` Laszlo Ersek
2018-10-14 14:51 ` Gao, Liming
2018-10-14 16:00 ` Leif Lindholm
2018-10-13 16:45 ` 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=B9726D6DCCFB8B4CA276A9169B02216D5213F5B7@SHSMSX103.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