mu
mu copied to clipboard
microsoft
Project Mu Documentation
The CI DSC lacks ARM and AARCH64 in SUPPORTED_ARCHITECTURES. Lets add these architectures where possible to get build and host unit test coverage. Example: `OemPkg\OemPkg.dsc:15: SUPPORTED_ARCHITECTURES = IA32|X64`
Many of the CI DSC's lack ARM and AARCH64 in their SUPPORTED_ARCHITECTURES. Lets add these architectures where possible to get build and host unit test coverage. Examples: AdvLoggerPkg\AdvLoggerPkg.dsc:14: SUPPORTED_ARCHITECTURES =...
After addition of VersionInfo feature to HelloWorld, I would expect Windows Explorer > Properties > Details tab to show version information (note, you must rename HelloWorld.efi to HelloWorld_.EXE_ for this...
They also are calling out VS2017 when our build actually uses vs2019 There is no user clickable link to see the builds.
There are 2 copies of UefiVariablesSupportLib.py in MU_PLUS. 1. [UefiTestingPkg copy](https://github.com/microsoft/mu_plus/blob/42bc853ecb2511f0684a5553f3c671e8b141ac23/UefiTestingPkg/AuditTests/UefiVarLockAudit/Windows/UefiVariablesSupportLib.py) 2. [DfciPkg copy](https://github.com/microsoft/mu_plus/blob/42bc853ecb2511f0684a5553f3c671e8b141ac23/DfciPkg/UnitTests/DfciTests/Support/Python/UefiVariablesSupportLib.py) Consider consolidation _**or**_ move to a PyTools Library?
In most of the Mu repos, the pip-requirements is pinning edk2 py extentions to version 12... `edk2-pytool-extensions==0.12.*` This should probably move forward
Is there any testing available for the Mu DFCI implementation for a BIOS Vendor?
This PR adds pipeline files that are a little verbose: https://github.com/microsoft/mu_basecore/pull/39 Optimize these.
If DSC has something like: !include $(PATH_FROM_NUGET_EXTDEP)/foo.inc then the BMP plugin will fail with: ERROR - Invalid file path C:\src\devices\$(PATH_FROM_NUGET_EXTDEP)/foo.inc
Over the past couple days I have seen a lot of questions and misunderstandings that Project Mu should try to clarify. * Why UEFI? * Can I replace the firmware...