Fork of ipxe; additional commands and features https://git.openslx.org/openslx-ng/ipxe.git/atom/src/util/.gitignore?h=openslx 2025-05-06T11:11:02+00:00 2025-05-06T11:11:02+00:00 Michael Brown 2025-05-06T11:07:38+00:00 urn:sha1:98646b9f016d9bff91a5c89f402aeb452ee7f84b Parsing ELF data is simpler if we don't have to build a single binary to handle both 32-bit and 64-bit ELF formats. Allow for separate 32-bit and 64-bit binaries built from util/zbin.c (as is already done for util/elf2efi.c). Signed-off-by: Michael Brown <mcb30@ipxe.org> 2021-02-12T22:08:41+00:00 Michael Brown 2021-02-12T21:56:53+00:00 urn:sha1:b539e9a7e95c3a481c686ffcf310c87bc1e19707 Support for building with the Intel C compiler (icc) was added in 2009 in the expectation that UEFI support would eventually involve compiling iPXE to EFI Byte Code. EFI Byte Code has never found any widespread use: no widely available compilers can emit it, Microsoft refuses to sign EFI Byte Code binaries for UEFI Secure Boot, and I have personally never encountered any examples of EFI Byte Code in the wild. The support for using the Intel C compiler has not been tested in over a decade, and would almost certainly require modification to work with current releases of the compiler. Simplify the build process by removing this old legacy code. Signed-off-by: Michael Brown <mcb30@ipxe.org> 2014-09-10T02:12:10+00:00 Michael Brown 2014-09-10T01:58:50+00:00 urn:sha1:5de37e124fd21c8f918f3fe26fc33a764709ead4 Add utility for constructing EFI fat binaries (dual 32/64-bit binaries, usable only on Apple EFI systems). This utility is not part of the standard build process. To use it: make util/efifatbin bin-i386-efi/ipxe.efi bin-x86_64-efi/ipxe.efi and then ./util/efifatbin bin-*-efi/ipxe.efi fat-ipxe.efi Requested-by: Brandon Penglase <bpenglase-ipxe@spaceservices.net> Tested-by: Brandon Penglase <bpenglase-ipxe@spaceservices.net> Signed-off-by: Michael Brown <mcb30@ipxe.org> 2010-05-31T02:11:57+00:00 Michael Brown 2010-05-30T14:29:05+00:00 urn:sha1:6c0e8c14be9546b49c097f5e6e8307bda3e7f5ac Add preprocessor magic to the error definitions to enable every error usage to be tracked. Signed-off-by: Michael Brown <mcb30@ipxe.org> 2009-03-26T07:27:19+00:00 Michael Brown 2009-03-10T17:50:01+00:00 urn:sha1:1c67623e37dada045e9b5d1f5e19b414cc79c3e3 2009-01-08T02:19:18+00:00 Michael Brown 2009-01-08T02:19:18+00:00 urn:sha1:fb72336fe642a9a6f0d45cc39e1303890fb8af05 2009-01-07T22:59:05+00:00 Michael Brown 2009-01-07T02:05:51+00:00 urn:sha1:314779eb369db746be5373b398111d5b746d67de elf2efi converts a suitable ELF executable (containing relocation information, and with appropriate virtual addresses) into an EFI executable. It is less tightly coupled with the gPXE build process and, in particular, does not require the use of a hand-crafted PE image header in efiprefix.S. elf2efi correctly handles .bss sections, which significantly reduces the size of the gPXE EFI executable. 2008-10-13T09:24:14+00:00 Michael Brown 2008-10-12T00:55:55+00:00 urn:sha1:81d92c6d34f9ce68f7c2bbd5b92352b3a631bcd0 We have EFI APIs for CPU I/O, PCI I/O, timers, console I/O, user access and user memory allocation. EFI executables are created using the vanilla GNU toolchain, with the EXE header handcrafted in assembly and relocations generated by a custom efilink utility. 2007-07-16T15:58:38+00:00 Michael Brown 2007-07-16T15:58:38+00:00 urn:sha1:048bbeeebcfce2eac0a21a8eaf44a6810d685032 2007-07-15T12:31:31+00:00 Michael Brown 2007-07-15T12:31:31+00:00 urn:sha1:a8780a4fe4695358db53888895df33c9093f92cf