From: Laszlo Ersek <lersek@redhat.com>
To: Shenglei Zhang <shenglei.zhang@intel.com>, edk2-devel@lists.01.org
Cc: "Jordan Justen" <jordan.l.justen@intel.com>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Julien Grall" <julien.grall@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2 05/10] OvmfPkg/README: Remove UNIXGCC
Date: Mon, 11 Feb 2019 12:07:52 +0100 [thread overview]
Message-ID: <8ac1db2e-3b38-f823-bc3b-c3791cff917c@redhat.com> (raw)
In-Reply-To: <20190211024809.20408-6-shenglei.zhang@intel.com>
On 02/11/19 03:48, Shenglei Zhang wrote:
> Remove UNIXGCC in OvmfPkgIa32.dsc, OvmfPkgIa32X64.dsc
> and OvmfPkgX64.dsc.
> Remove content related to UNIXGCC in README.
> https://bugzilla.tianocore.org/show_bug.cgi?id=1377
>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Anthony Perard <anthony.perard@citrix.com>
> Cc: Julien Grall <julien.grall@linaro.org>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Shenglei Zhang <shenglei.zhang@intel.com>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> ---
> OvmfPkg/OvmfPkgIa32.dsc | 1 -
> OvmfPkg/OvmfPkgIa32X64.dsc | 1 -
> OvmfPkg/OvmfPkgX64.dsc | 1 -
> OvmfPkg/README | 19 -------------------
> 4 files changed, 22 deletions(-)
>
> diff --git a/OvmfPkg/OvmfPkgIa32.dsc b/OvmfPkg/OvmfPkgIa32.dsc
> index aee19b75d7..7872ead8de 100644
> --- a/OvmfPkg/OvmfPkgIa32.dsc
> +++ b/OvmfPkg/OvmfPkgIa32.dsc
> @@ -61,7 +61,6 @@
> !endif
>
> [BuildOptions]
> - GCC:*_UNIXGCC_*_CC_FLAGS = -DMDEPKG_NDEBUG
> GCC:RELEASE_*_*_CC_FLAGS = -DMDEPKG_NDEBUG
> INTEL:RELEASE_*_*_CC_FLAGS = /D MDEPKG_NDEBUG
> MSFT:RELEASE_*_*_CC_FLAGS = /D MDEPKG_NDEBUG
> diff --git a/OvmfPkg/OvmfPkgIa32X64.dsc b/OvmfPkg/OvmfPkgIa32X64.dsc
> index 90cbd8e341..eef8ae25f3 100644
> --- a/OvmfPkg/OvmfPkgIa32X64.dsc
> +++ b/OvmfPkg/OvmfPkgIa32X64.dsc
> @@ -61,7 +61,6 @@
> !endif
>
> [BuildOptions]
> - GCC:*_UNIXGCC_*_CC_FLAGS = -DMDEPKG_NDEBUG
> GCC:RELEASE_*_*_CC_FLAGS = -DMDEPKG_NDEBUG
> INTEL:RELEASE_*_*_CC_FLAGS = /D MDEPKG_NDEBUG
> MSFT:RELEASE_*_*_CC_FLAGS = /D MDEPKG_NDEBUG
> diff --git a/OvmfPkg/OvmfPkgX64.dsc b/OvmfPkg/OvmfPkgX64.dsc
> index 83d16eb00b..6d5623857c 100644
> --- a/OvmfPkg/OvmfPkgX64.dsc
> +++ b/OvmfPkg/OvmfPkgX64.dsc
> @@ -61,7 +61,6 @@
> !endif
>
> [BuildOptions]
> - GCC:*_UNIXGCC_*_CC_FLAGS = -DMDEPKG_NDEBUG
> GCC:RELEASE_*_*_CC_FLAGS = -DMDEPKG_NDEBUG
> INTEL:RELEASE_*_*_CC_FLAGS = /D MDEPKG_NDEBUG
> MSFT:RELEASE_*_*_CC_FLAGS = /D MDEPKG_NDEBUG
> diff --git a/OvmfPkg/README b/OvmfPkg/README
> index 68ce0750af..c014d07bfb 100644
> --- a/OvmfPkg/README
> +++ b/OvmfPkg/README
> @@ -402,25 +402,6 @@ main firmware (MAINFV) into RAM memory at address 0x800000. The
> remaining OVMF firmware then uses this decompressed firmware
> volume image.
>
> -=== UNIXGCC Debug ===
> -
> -If you build with the UNIXGCC toolchain, then debugging will be disabled
> -due to larger image sizes being produced by the UNIXGCC toolchain. The
> -first choice recommendation is to use GCC48 or newer instead.
> -
> -If you must use UNIXGCC, then you can override the build options for
> -particular libraries and modules in the .dsc to re-enable debugging
> -selectively. For example:
> - [Components]
> - OvmfPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf {
> - <BuildOptions>
> - GCC:*_*_*_CC_FLAGS = -UMDEPKG_NDEBUG
> - }
> - MdeModulePkg/Universal/BdsDxe/BdsDxe.inf {
> - <BuildOptions>
> - GCC:*_*_*_CC_FLAGS = -UMDEPKG_NDEBUG
> - }
> -
> === UEFI Windows 7 & Windows 2008 Server ===
>
> * One of the '-vga std' and '-vga qxl' QEMU options should be used.
>
Looks good, thanks! (+Phil)
Laszlo
next prev parent reply other threads:[~2019-02-11 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 2:47 [PATCH v2 00/10] Remove unused tool chain configuration Shenglei Zhang
2019-02-11 2:48 ` [PATCH v2 01/10] BaseTools/tools_def.template: Remove VS2003 and VS2005 Shenglei Zhang
2019-02-11 2:48 ` [PATCH v2 02/10] OptionRomPkg/ReadMe.txt: Remove VS2005 Shenglei Zhang
2019-02-11 2:48 ` [PATCH v2 03/10] BaseTools/tools_def.template: Remove DDK3790 Shenglei Zhang
2019-02-11 2:48 ` [PATCH v2 04/10] BaseTools/tools_def.template: Remove UNIXGCC Shenglei Zhang
2019-02-11 2:48 ` [PATCH v2 05/10] OvmfPkg/README: " Shenglei Zhang
2019-02-11 9:00 ` Ard Biesheuvel
2019-02-11 11:07 ` Laszlo Ersek [this message]
2019-02-11 2:48 ` [PATCH v2 06/10] BaseTools: Update MYTOOLS Shenglei Zhang
2019-02-11 2:48 ` [PATCH v2 07/10] BaseTools/tools_def.template: Remove ELFGCC Shenglei Zhang
2019-02-11 2:48 ` [PATCH v2 08/10] BaseTools/tools_def.template: Remove CYGGCC Shenglei Zhang
2019-02-11 2:48 ` [PATCH v2 09/10] OptionRomPkg/ReadMe.txt: " Shenglei Zhang
2019-02-11 2:48 ` [PATCH v2 10/10] BaseTools/build_rule.template: Remove GCCLD Shenglei Zhang
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=8ac1db2e-3b38-f823-bc3b-c3791cff917c@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