Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
This branch is 72 commits ahead, 4 commits behind utshina:master.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time
gnu-efi @ b1c7a1c

UEFI:SIMPLE - EFI development made easy

A simple UEFI "Hello World!" style application that can:

  • be compiled on Windows or Linux, using Visual Studio 2019, MinGW or gcc.
  • be compiled for x86_32, x86_64, ARM or ARM64/AARCH64 targets
  • be tested on the fly, through a QEMU + OVMF or QEMU_EFI virtual machine.


  • Visual Studio 2019 or gcc/make
  • QEMU v2.7 or later (NB: You can find QEMU Windows binaries here)
  • git
  • wget, unzip, if not using Visual Studio

Sub-Module initialization

For convenience, the project relies on the gnu-efi library, so you need to initialize the git submodule either through git commandline with:

git submodule init
git submodule update

Or, if using a UI client (such as TortoiseGit) by selecting Submodule Update in the context menu.

Compilation and testing

If using Visual Studio, just press F5 to have the application compiled and launched in the QEMU emulator.

If using MinGW or Linux, issue the following from a command prompt:


If needed you can also add ARCH=<arch> and CROSS_COMPILE=<tuple>, e.g.:

  • make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
  • make ARCH=aa64 CROSS_COMPILE=aarch64-linux-gnu-

where <arch> can be x64, ia32, arm or aa64.

You can also add qemu as your make target to run the application under QEMU, in which case a relevant UEFI firmware (OVMF for x86 or QEMU_EFI for Arm) will be automatically downloaded to run your application against it.

Visual Studio 2019 and ARM/ARM64 support

Please be mindful that, to enable ARM or ARM64 compilation support in Visual Studio 2019, you MUST go to the Individual components screen in the setup application and select the ARM/ARM64 build tools there, as they do NOT appear in the default Workloads screen:

VS2019 Individual Components


No releases published


No packages published


  • Makefile 35.6%
  • VBScript 35.1%
  • C 29.3%