Eugene -
We found this also when because there are DEBUG macros in the serial port
library. Is this the root cause of what you found? We finally had to hack the
library constructors, but it was messy.
Tim
From: Cohen, Eugene [mailto:eug...@hp.com]
Sent: Tuesday, August 26, 2014 7:49 AM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] Circular Dependency Between DxePrintLibPrint2Protocol and
BaseDebugLibSerialPort
Dear maintainers of DebugLib and PrintLib,
It looks like we have a circular dependency between the
DxePrintLibPrint2Protocol library (which uses ASSERT) and
BaseDebugLibSerialPort library (which uses AsciiSPrint):
1><myplatform>.dsc(...) : error F002: Library
[c:\edk2\MdeModulePkg\Library\DxePrintLibPrint2Protocol\DxePrintLibPrint2Protocol.inf]
with constructors has a cycle
1> consumed by
c:\edk2\MdePkg\Library\BaseDebugLibSerialPort\BaseDebugLibSerialPort.inf
so it seems that this library combination is incompatible. Is there a
preferred way to resolve this?
I see some platforms use the status code variant of DebugLib
(PeiDxeDebugLibReportStatusCode) but I'd prefer a solution that allows us to
keep using the simple BaseDebugLibSerialPort.
Thanks,
Eugene
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
