On 10/12/18 15:27, Leif Lindholm wrote: > On Thu, Oct 11, 2018 at 10:43:57AM -0700, stephano wrote:
>> Switching to Standard C Types >> ----------------------------- >> Both Shawn and Nate mentioned that the current system has been in place for >> a long time and some people prefer the current setup. I can start an email >> discussion around this issue specifically if anyone feels strongly that we >> should be using standard types. > > So, I don't think we made it this far down the agenda on the US-EU > call. > > One way would be to simply explicitly permit it, possibly with the > constraint that every module needs to pick one and stick with it, > unless people object. > > I think we'll want to discuss this in a US-EU call as well. I'm playing devil's advocate here -- because, in general, I'm a fan of sticking with standard C as much as possible --, but I see a big obstacle in the way. That obstacle is "Table 5. Common UEFI Data Types", in the UEFI spec. Until a good portion of that table is expressed in terms of standard C types as well (expanding upon the current definitions), possibly in an edk2-level spec (i.e. not necessarily in the UEFI spec itself), I think there's no chance to enable standard C types in edk2 *meaningfully*. Because, as soon as you have to call a PI or UEFI interface, you'll have to stick with the PI/UEFI spec types anyway. >> Using Git Submodules (like we do with OpenSSL) >> -------------------- > > We didn't make it here either. What would we use it _for_? > I think the openssl case makes a lot of sense, but what else? We embed a bunch of other projects (libraries, mainly): - Oniguruma - Brotli - fdt - LZMA SDK - ... Thanks Laszlo _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
