-----------------------------------------\r
\r
Cygwin is a POSIX style operating environment for Windows. It is possible to\r
-compile the EDK 2 using gcc and cygwin. There are a few extra steps necessary\r
-to make this happen. \r
-Compiling under cygwin is slow, because the underlying file accesses are slow\r
-in cygwin. For this reason, we do not encourage the use of cygwin. A true unix\r
-system will be a superior choice for those wishing to compile with gcc.\r
+compile the EDK 2 using gcc and cygwin. Compiling under cygwin is slow, because \r
+the underlying file accesses are slow in cygwin. For this reason, we do not \r
+encourage the use of cygwin. A true unix system will be a superior choice for \r
+those wishing to compile with gcc.\r
\r
Make sure that you select the e2fsprogs development package when you install\r
cygwin. It is necessary for the GenFvImage tool.\r
\r
Currently gcc support is limited to IA-32 builds, generating IA-32 PE32 images. \r
\r
-The X64 bit (Intel 64, etc.) support under the gcc compiler does not support the EFIAPI calling convention (as defined in the UEFI 2.0 specification Chapter 2), so it is not possible to build a working EFI image for an X64 environment. Since the x64 gcc does not support the EFIAPI calling convention the x64 tools do not support generating a PE32+ image. The EFIAPI calling convention is very similar to the Microsoft x64 calling convention.\r
+The X64 bit (Intel 64, etc.) support under the gcc compiler does not support the EFIAPI \r
+calling convention (as defined in the UEFI 2.0 specification Chapter 2), so it is not \r
+possible to build a working EFI image for an X64 environment. Since the x64 gcc does \r
+not support the EFIAPI calling convention the x64 tools do not support generating a \r
+PE32+ image. The EFIAPI calling convention is very similar to the Microsoft x64 \r
+calling convention.\r
\r
On Itanium® Processors the gcc compiler does not support generating a PE32+ image.\r
\r
projects / mirror_edk2.git / blobdiff