> On Jun 22, 2016, at 12:38 PM, Marvin H?user <[email protected]> > wrote: > > Dear EDK2 developers, > > For an experimental project, I'm currently attempting to write a library > wrapper for the disassembler library 'Capstone' in a similar manner to > CryptoPkg's OpensslLib. As most C libraries, it also depends on the standard > headers, which are not provided by 'stock' EDK2. My first guess has been to > use StdLib, though its description states: > 'Due to the execution environment built by the StdLib component, execution as > a UEFI driver can cause system stability issues.' > > Inspecting OpensslLib I discovered that CryptoPkg deploys its own include > files for StdLib. Though, from your experience, what are the issues with > using StdLibPkg with DXE/UEFI drivers? It might be nice to reduce duplicate > code, though I honestly don't know anything about StdLibPkg and its > implementation and would be thankful for some insight on that manner. >
Marvin, The edk2 StdLib has a dependency on EFI Shell interfaces and this is what makes it not work properly as a driver. If you cd int StdLib and `git grep shell` you will see the platform abstractions are not pure EFI, but Shell oriented. The Shell adds concepts like environment variables and volume names that don't exist in EFI. Thanks, Andrew Fish > Thank you in advance for your time! > > Regards, > Marvin. > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
