On Jan 9, 2014, at 1:19 PM, Kirkendall, Garrett <[email protected]>
wrote:
> Should we force Little Endian as well since EFI has taken the Little Endian
> stance?
>
Good point. We should make sure all the places are consistent. In the C code
and the Python BaseTools.
> I know there are a few places in the build tools that pack and unpack data,
> and I assume we should try to force consistency wherever possible. Just in
> case the dream comes true and UEFI takes over the firmware world and we end
> up with a build environment that is natively Big Endian.
>
Given this is Python it is really more about the OS your are building from.
Cross compilers do exist, so it is best not to make assumptions.
Thanks,
Andrew Fish
> GARRETT KIRKENDALL <image004.png>
> SMTS Firmware Engineer | AMD Technology & Engineering
> 7171 Southwest Parkway, Austin, TX 78735 USA
> <image003.png> facebook | amd.com
>
> From: Andrew Fish [mailto:[email protected]]
> Sent: Thursday, January 09, 2014 12:03 AM
> To: Liu, Yingke D
> Cc: [email protected];
> [email protected]
> Subject: Re: [edk2-buildtools] Portability bug in BuildReport.py
>
>
> On Jan 8, 2014, at 10:00 PM, Liu, Yingke D <[email protected]> wrote:
>
>
> Hi Andrew,
>
> Thanks for your explanation. The patch is attached according to your comments.
>
>
> Dennis,
>
> The patch looks good.
>
> Thanks,
>
> Andrew Fish
>
>
> Thanks,
> Dennis
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
edk2-buildtools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-buildtools-devel
