Branch: refs/heads/master
Home: https://github.com/tianocore/edk2
Commit: b197541f2946d8dd4685243a32599b631e574947
https://github.com/tianocore/edk2/commit/b197541f2946d8dd4685243a32599b631e574947
Author: Mike Beaton <[email protected]>
Date: 2025-11-21 (Fri, 21 Nov 2025)
Changed paths:
M ArmVirtPkg/ArmVirtQemu.dsc
M ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc
M ArmVirtPkg/ArmVirtQemuKernel.dsc
M NetworkPkg/NetworkDynamicPcds.dsc.inc
M OvmfPkg/CloudHv/CloudHvX64.fdf
M OvmfPkg/Microvm/MicrovmX64.fdf
M OvmfPkg/OvmfPkgIa32X64.fdf
M OvmfPkg/OvmfPkgX64.fdf
Log Message:
-----------
OvmfPkg,ArmVirtPkg,NetworkPkg: Fix build with -D NETWORK_ENABLE=0
Previous PR https://github.com/tianocore/edk2/pull/6087 restored the
ability to build OvmfPkg with -D NETWORK_ENABLE=0.
b3b3cfab7eb52acd77558a9727196e30d05d1f2a has broken it again, since the
.dsc references to OvmfPkg/VirtioNetDxe/VirtioNet.inf were moved from
outside !if $(NETWORK_ENABLE) == TRUE to inside it, while the .fdf
references remained outside.
In discussion in https://github.com/tianocore/edk2/pull/11719 it was
decided to move the .fdf references inside the conditional, i.e. not to
include VirtioNetDxe unless the rest of the network stack is being built.
Removal of VirtioNetDxe driver on -D NETWORK_ENABLE=0 has only
been applied to those packages which are already using
OvmfPkg/Dsc/Includes/NetworkComponents.dsc.inc.
f9408b7cc160030c3bb9627c8086a792cc2d046c introduces new PCDs which also
need to be moved inside a NETWORK_ENABLE test in order to allow building
with -D NETWORK_ENABLE=0, which is also done here.
Continuous-integration-options: PatchCheck.ignore-multi-package
Signed-off-by: Mike Beaton <[email protected]>
To unsubscribe from these emails, change your notification settings at
https://github.com/tianocore/edk2/settings/notifications
_______________________________________________
edk2-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-commits
