Leif:
  I think the first step is to update edk2 DSC files to use MdeModulePkg 
library. Could you enter into one bug for it? 

Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Leif Lindholm
> Sent: Tuesday, November 15, 2016 1:17 AM
> To: edk2-devel (edk2-devel@lists.01.org) <edk2-devel@lists.01.org>; Gao,
> Liming <liming....@intel.com>; Wu, Hao A <hao.a...@intel.com>
> Cc: Kinney, Michael D <michael.d.kin...@intel.com>; Tian, Feng
> <feng.t...@intel.com>; Andrew Fish <af...@apple.com>; Zeng, Star
> <star.z...@intel.com>
> Subject: [edk2] LzmaCustomDecompressLib and
> PeiDxeDebugLibReportStatusCode
> 
> Hi all,
> 
> Digging through the tree, I spotted we have duplicate instances of the
> above - one set in MdeModulePkg/Library/ and one in
> IntelFrameworkModulePkg.
> 
> Looking though the log, I found the commit message explaining the situation:
> ---
> MdeModulePkg: Add two library instances
> 
>     Copy below two library instances from IntelFrameworkModulePkg to
> MdeModulePkg. Then, Platform dsc can
>     refer to them from MdeModulePkg, and remove the dependency of
> IntelFrameworkModulePkg. The ones in
>     IntelFrameworkModulePkg are still kept for compatibility.
>     1. PeiDxeDebugLibReportStatusCode
>     2. LzmaCustomDecompressLib
> ---
> 
> Even in the main tree, both versions of these are used.
> 
> Diffing the clones, 1) has diverged, with 8f77081 going into
> MdeModulePkg and d5cbc27 into IntelFrameworkModulePkg. The
> functionality is identical, but the code is not.
> 
> Can we re-evaluate the need to keep the "compatibility" copy around,
> to reduce risk of further diversion?
> 
> Regards,
> 
> Leif
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Reply via email to