OSDev.org

Hey all,

I'm getting started with UEFI applications for a kernel project I'm working on and running into some issues with the first compilation. I've generally followed the UEFI app bare bones guide to a T, but I'm consistently hitting my head on some undefined reference errors in the final of three compilation steps (the linking of the UEFI main executable and data.o). The UEFI application I'm attempting to compile is a basic "Hello, world!" consisting of the following:



Build environment is a rather new install of Ubuntu 23.04, gcc-mingw-w64 version 12.2.0, binutils-mingw-w64 version 2.39.90. I've successfully installed GNU-EFI as well as made the prescribed modifications to gnuefi/lib/data.c. The error occurs on the final leg of the three-part compilation:



First order of business was to check to ensure I got the paths right - GNU-EFI apparently installs to /usr/lib on Ubuntu, as confirmed by dpkg:



At this point, I'm a bit stumped. I can obviously tell something's going on with the linking (not including or correctly binding an EFI lib), but I'm lost on how to address the matter further. I found this thread which has a similar issue, although I'm uncertain what the resolution ultimately was or whether or not it applies to this particular route (using the MinGW cross-compiler). I tried my hand at cobbling a Makefile for the process, although this gives me a different series of errors and I'm almost certain I messed something up somewhere. I'm by no means a novice to C/C++, but I have virtually zero experience with make - I've always gotten by using built-in IDE build systems.



Any ideas? As is the case 90% of the time, I'm sure it boils down to some simple oversight of mine somewhere.

There is no "InitializeLib" or "Print" function in UEFI.

These functions are provided by gnu-efi's utility library, and the guide you followed specifically states: "This example does not link against GNU-EFI or follow its build process; only the headers are used."

Well, I expected it to be a silly mistake, but I didn't think I would manage to checkmate myself in one.

Are there any functions I can depend on the EFI headers providing, or are all going to need to be implemented via uefi_call_wrapper()? I did a quick cat of the headers and they look to be mostly types, defines, and GUIDs.

EFI does not provide any functions; instead you will find function pointers from the child members of the system table. You already have two that you are calling in your code: ST->ConIn->Reset and ST->ConIn->ReadKeyStroke.

Instead of reading the UEFI headers, you should read the UEFI specification which better describes what functions are available from different objects, and which ones you will likely want to use.

You do not need gnu-efi's uefi_call_wrapper, either, as you are using a mingw toolchain and all that wrapper does is provide the Microsoft calling convention that UEFI expects.