On 4/15/2020 8:04 AM, Laszlo Ersek wrote:
I figure you attempted the DEBUG_ON_SERIAL_PORT build because without it
you get no debug output at all (due to the default
PlatformDebugLibIoPort resolution, which produces no logs on Xen).
I just attempted the DEBUG_ON_SERIAL_PORT build because that's how I do
the other DEBUG OVMF builds and was running the following basic build
script to make sure my bhyve changes weren't breaking things.
build -p OvmfPkg/OvmfPkgX64.dsc -a X64 -t GCC5 -b RELEASE
build -p OvmfPkg/OvmfPkgX64.dsc -a X64 -t GCC5 -b DEBUG
-DDEBUG_ON_SERIAL_PORT=TRUE
build -p OvmfPkg/OvmfPkgX64.dsc -a X64 -t GCC5 -b NOOPT
build -p OvmfPkg/OvmfPkgIa32.dsc -a IA32 -t GCC5 -b RELEASE
build -p OvmfPkg/OvmfPkgIa32.dsc -a IA32 -t GCC5 -b DEBUG
-DDEBUG_ON_SERIAL_PORT=TRUE
build -p OvmfPkg/OvmfPkgIa32.dsc -a IA32 -t GCC5 -b NOOPT
build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 -b RELEASE
build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 -b DEBUG
-DDEBUG_ON_SERIAL_PORT=TRUE
build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 -b NOOPT
build -p OvmfPkg/OvmfXen.dsc -a X64 -t GCC5 -b RELEASE
build -p OvmfPkg/OvmfXen.dsc -a X64 -t GCC5 -b DEBUG
-DDEBUG_ON_SERIAL_PORT=TRUE
build -p OvmfPkg/OvmfXen.dsc -a X64 -t GCC5 -b NOOPT
build -p BhyvePkg/BhyvePkgX64.dsc -a X64 -t GCC5 -b RELEASE
build -p BhyvePkg/BhyvePkgX64.dsc -a X64 -t GCC5 -b DEBUG
-DDEBUG_ON_SERIAL_PORT=TRUE
build -p BhyvePkg/BhyvePkgX64.dsc -a X64 -t GCC5 -b NOOPT
--
Rebecca Cran
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#57413): https://edk2.groups.io/g/devel/message/57413
Mute This Topic: https://groups.io/mt/73015916/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
