UEFI: Difference between revisions

It uses POSIX style typedefs (like ''uintn_t'' instead of ''UINTN''), and it does not ship with the standard EFI headers. You can still get interfaces not covered by POSIX-UEFI (such as GOP) by installing the EFI headers from GNU-EFI or EDK2. Also, it compiles with the MS ABI, meaning that UEFI services can be called natively (i.e., without uefi_call_wrapper) so long as your apps are compiled with it as well.

The traditional "Hello, world" UEFI program goes like this.

#include <uefi.h>

return 0;

}

Makefile looks like this:

<syntaxhighlight lang="make">

The traditional "Hello, world" UEFI program is shown below.

#include <efi.h>

#include <efilib.h>

return EFI_SUCCESS;

}

A few notes:

The uefi-run application is useful for quick testing. It creates a temporary FAT image containing your EFI application and starts qemu.

$ uefi-run -b /path/to/OVMF.fd -q /path/to/qemu app.efi -- <extra_qemu_args>

uefi-run is not currently packaged for any distribution. You can install it using cargo (the Rust package manager) though ("cargo install uefi-run").