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 applications that do not rely on ShellPkg (example:
SysPrep application that might want to use Redfish, which
depends on C standard library)?
* What about drivers/libraries that rely on C standard library?
* How is that compatible with EDK2 BSD-2-Clause-Patent?
2. Torito C is pre-compiled.
* How can I verify what was actually implemented inside? Industry
would have to trust your tests, perform own set of tests or/and
disassemble it (doable, but unacceptable effort-wise).
Unless those problems are solved, I simply cannot use it.
Thanks,
Maciej
On 14-Nov-21 20:51, Kilian Kegel wrote:
Hi All,
as announced last summer, I’d like to start a comprehensive tutorial on
how to use Standard C / ANSI C in the UEFI environment and how to
design and implement
such a library for Shell and POST usage.
Since most parts of that comprehensive work are already done,
I will report, demonstrate and discuss implementation principles and
details on edk2.groups.io
as a kind of “blog” on a biweekly basis.
Please checkout my first CdePkgBlog
https://github.com/tianocore/edk2-staging/tree/CdePkg/blogs/2021-11-14#cdepkgblog-2021-11-14
and enjoy the breathtaking build speed if compiler and linker are used
exclusively to create MY LEGACY TOOLBOX,
a handy set of one-trick-ponies that I have been using for about 25 years.
Have fun,
Kilian
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#83915): https://edk2.groups.io/g/devel/message/83915
Mute This Topic: https://groups.io/mt/87053945/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
