From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: Laszlo Ersek <lersek@redhat.com>, Bruce Cran <bruce@cran.org.uk>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [PATCH] Add NOOPT build targets to OvmfPkg for source level debugging
Date: Tue, 11 Oct 2016 00:51:38 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D4F399F7F@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <55f70d94-6c60-52e6-2934-4582ba6b2920@redhat.com>
Looks good to me.
When the BaseTools' support for NOOPT is reviewed and pushed, I will inform to you. Thanks.
Best Regards,
Zhu Yonghong
-----Original Message-----
From: Laszlo Ersek [mailto:lersek@redhat.com]
Sent: Tuesday, October 11, 2016 12:30 AM
To: Bruce Cran <bruce@cran.org.uk>
Cc: edk2-devel@lists.01.org <edk2-devel@ml01.01.org>; Zhu, Yonghong <yonghong.zhu@intel.com>
Subject: Re: [PATCH] Add NOOPT build targets to OvmfPkg for source level debugging
On 10/10/16 18:27, Laszlo Ersek wrote:
> On 10/10/16 17:43, Bruce Cran wrote:
>>
>>
>> 0001-Add-NOOPT-build-targets-to-OvmfPkg-for-source-level-.patch
>>
>>
>> From ef7b3dfe26bb7748d838974af57cd73e40e24c94 Mon Sep 17 00:00:00
>> 2001
>> From: Bruce Cran <Bruce.Cran@sandisk.com>
>> Date: Mon, 10 Oct 2016 09:35:50 -0600
>> Subject: [PATCH] Add NOOPT build targets to OvmfPkg for source level
>> debugging
>>
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Cc: Yonghong Zhu <yonghong.zhu@intel.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Signed-off-by: Bruce Cran <bruce.cran@sandisk.com>
>> ---
>> OvmfPkg/OvmfPkgIa32.dsc | 2 +-
>> OvmfPkg/OvmfPkgIa32X64.dsc | 2 +-
>> OvmfPkg/OvmfPkgX64.dsc | 2 +-
>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/OvmfPkg/OvmfPkgIa32.dsc b/OvmfPkg/OvmfPkgIa32.dsc index
>> 7213197..41500ca 100644
>> --- a/OvmfPkg/OvmfPkgIa32.dsc
>> +++ b/OvmfPkg/OvmfPkgIa32.dsc
>> @@ -26,7 +26,7 @@
>> DSC_SPECIFICATION = 0x00010005
>> OUTPUT_DIRECTORY = Build/OvmfIa32
>> SUPPORTED_ARCHITECTURES = IA32
>> - BUILD_TARGETS = DEBUG|RELEASE
>> + BUILD_TARGETS = NOOPT|DEBUG|RELEASE
>> SKUID_IDENTIFIER = DEFAULT
>> FLASH_DEFINITION = OvmfPkg/OvmfPkgIa32.fdf
>>
>> diff --git a/OvmfPkg/OvmfPkgIa32X64.dsc b/OvmfPkg/OvmfPkgIa32X64.dsc
>> index c27024a..1bd4b21 100644
>> --- a/OvmfPkg/OvmfPkgIa32X64.dsc
>> +++ b/OvmfPkg/OvmfPkgIa32X64.dsc
>> @@ -26,7 +26,7 @@
>> DSC_SPECIFICATION = 0x00010005
>> OUTPUT_DIRECTORY = Build/Ovmf3264
>> SUPPORTED_ARCHITECTURES = IA32|X64
>> - BUILD_TARGETS = DEBUG|RELEASE
>> + BUILD_TARGETS = NOOPT|DEBUG|RELEASE
>> SKUID_IDENTIFIER = DEFAULT
>> FLASH_DEFINITION = OvmfPkg/OvmfPkgIa32X64.fdf
>>
>> diff --git a/OvmfPkg/OvmfPkgX64.dsc b/OvmfPkg/OvmfPkgX64.dsc index
>> c34b266..460f7bb 100644
>> --- a/OvmfPkg/OvmfPkgX64.dsc
>> +++ b/OvmfPkg/OvmfPkgX64.dsc
>> @@ -26,7 +26,7 @@
>> DSC_SPECIFICATION = 0x00010005
>> OUTPUT_DIRECTORY = Build/OvmfX64
>> SUPPORTED_ARCHITECTURES = X64
>> - BUILD_TARGETS = DEBUG|RELEASE
>> + BUILD_TARGETS = NOOPT|DEBUG|RELEASE
>> SKUID_IDENTIFIER = DEFAULT
>> FLASH_DEFINITION = OvmfPkg/OvmfPkgX64.fdf
>>
>> -- 2.10.0
>>
>
> Looks good to me:
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>
> but we should hold it until Yonghong's v4 is posted / reviewed / pushed.
(maybe the subject can be rewritten as
OvmfPkg: add NOOPT build target for source level debugging
but I can do that later when I commit the patch.)
prev parent reply other threads:[~2016-10-11 0:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 15:43 [PATCH] Add NOOPT build targets to OvmfPkg for source level debugging Bruce Cran
2016-10-10 16:27 ` Laszlo Ersek
2016-10-10 16:29 ` Laszlo Ersek
2016-10-10 20:27 ` Bruce Cran
2016-10-12 7:38 ` Laszlo Ersek
2016-10-11 0:51 ` Zhu, Yonghong [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=B9726D6DCCFB8B4CA276A9169B02216D4F399F7F@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