From: "Li, Yi" <yi1.li@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: [edk2-devel] Question about limit size of OvmfPkg NOOPT build
Date: Mon, 12 Jun 2023 06:52:36 +0000 [thread overview]
Message-ID: <SJ1PR11MB62279BAD44F8D32DBD29214BC554A@SJ1PR11MB6227.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Hello all,
I am working on OPENSSL30 upgrade of CryptoPkg.
The upgrade of the OPENSSL submodule will increase the size of binaries and break the CI build check: PlatformCI_OvmfPkg_Ubuntu_GCC5_PR (Platform_CI OVMF_IA32X64_FULL_NOOPT):
https://github.com/tianocore/edk2/pull/4391/
The size change is hard to avoid, can we skip this build of GCC just like we did for VS2019?
https://github.com/tianocore/edk2/blob/8314a85893f5b75baa0031a5138028188a626243/OvmfPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml#L112-L123
OvmfPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml#L112-L123:
# This currently creates a very large image which is too big for the FDF declared range
# Ovmf maintainers suggest to skip this build for now.
#
# OVMF_IA32X64_FULL_NOOPT:
# Build.File: "$(package)/PlatformCI/PlatformBuild.py"
# Build.Arch: "IA32,X64"
# Build.Flags: "BLD_*_SECURE_BOOT_ENABLE=1 BLD_*_SMM_REQUIRE=1 BLD_*_TPM2_ENABLE=1 BLD_*_NETWORK_TLS_ENABLE=1 BLD_*_NETWORK_IP6_ENABLE=1 BLD_*_NETWORK_HTTP_BOOT_ENABLE=1"
# Build.Target: "NOOPT"
# Run.Flags: $(run_flags)
# Run: $(should_run)
Regards,
Yi
[-- Attachment #2: Type: text/html, Size: 4509 bytes --]
next reply other threads:[~2023-06-12 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 6:52 Li, Yi [this message]
2023-06-14 7:45 ` [edk2-devel] Question about limit size of OvmfPkg NOOPT build Yao, Jiewen
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=SJ1PR11MB62279BAD44F8D32DBD29214BC554A@SJ1PR11MB6227.namprd11.prod.outlook.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