gt;;
tim.le...@insyde.com; Mike Kinney
<mailto:michael.d.kin...@intel.com>; af...@apple.com; Leif Lindholm
<mailto:l...@nuviainc.com>; Richardson, Brian
<mailto:brian.richard...@intel.com>
*Subject: *Re: [edk2-devel] CdePkgBlog 2021-11-14
Hi Kilian,
From my point of view, the
ntel.com>;
af...@apple.com; Leif Lindholm <mailto:l...@nuviainc.com>; Richardson,
Brian <mailto:brian.richard...@intel.com>
*Subject: *Re: [edk2-devel] CdePkgBlog 2021-11-14
Hi Kilian,
From my point of view, the main problem with adoption of CdePkg to
EDK2 is that it relies on To
m Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows
>
>
>
> *From: *Rabeda, Maciej
> *Sent: *Monday, November 22, 2021 05:31 PM
> *To: *devel@edk2.groups.io; kilian_ke...@outlook.com
> *Cc: *Rebecca Cran ; tim.le...@insyde.com; Mike
> Kinney ; af...@appl
com>;
af...@apple.com<mailto:af...@apple.com>; Leif
Lindholm<mailto:l...@nuviainc.com>; Richardson,
Brian<mailto:brian.richard...@intel.com>
Subject: Re: [edk2-devel] CdePkgBlog 2021-11-14
Hi Kilian,
>From my point of view, the main problem with adoption of CdePkg to
Hi Kilian,
From my point of view, the main problem with adoption of CdePkg to EDK2
is that it relies on Torito C library.
1. Torito C library License
(https://github.com/KilianKegel/toro-C-Library/blob/master/LICENSE.md)
only allows for creating UEFI Shell applications.
* What about
