You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MODULE_TYPE is BASE, but the library claims to be a MM_STANDALONE instance of the AdvancedLoggerLib library class. The MODULE_TYPE being BASE and it only applying to MM_STANDALONE is not a problem. However, it if truly does only apply to MM_STANDALONE, it should apply that module type restriction in the LIBRARY_CLASS value. For example:
LIBRARY_CLASS = AdvancedLoggerLib | MM_STANDALONE
Expected Behavior
Library is consistent, builds, and documented accurately.
Is there an existing issue for this?
Current Behavior
Arm related support has had a few bugs/points of confusion recently identified.
ARM
andAARCH64
code exists in the package butAdvLoggerPkg.dsc
does not list those asSUPPORTED_ARCHITECTURES
.AdvLoggerPkg/Library/AdvancedLoggerLib/BaseArm/AdvancedLoggerLib.inf
lists the following as valid architectures but the library instance only claims to support "Arm" otherwise (in theBaseArm
directory). Should this only beAARCH64
for clarity?MODULE_TYPE
isBASE
, but the library claims to be aMM_STANDALONE
instance of theAdvancedLoggerLib
library class. TheMODULE_TYPE
beingBASE
and it only applying toMM_STANDALONE
is not a problem. However, it if truly does only apply toMM_STANDALONE
, it should apply that module type restriction in theLIBRARY_CLASS
value. For example:LIBRARY_CLASS = AdvancedLoggerLib | MM_STANDALONE
Expected Behavior
Library is consistent, builds, and documented accurately.
Steps To Reproduce
N/A
Build Environment
Version Information
Urgency
Medium
Are you going to fix this?
Someone else needs to fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
The text was updated successfully, but these errors were encountered: