-If you want to build the rEFInd binary but not the drivers and if you're
-using Linux, GNU-EFI is the easiest way to do the job. I don't describe its
-setup here because it's likely to be fairly easy. If your distribution
-provides a recent enough version, you should be able to install a package
-called gnu-efi and be done with it. If not, you'll need to download the
-source code tarball, build it, and install it. This process is fairly
-typical of Linux packages. Read the GNU-EFI documentation if you need help.
-If you're using GNU-EFI, you can skip the rest of this section.
-
-To build the EFI drivers, the TianoCore toolkit is required. You might also
-want to use it if you have problems with GNU-EFI or if you want to build
-rEFInd on a non-Linux platform. Unfortunately, the TianoCore toolkit is
-weird by Linux programming standards. It's also quite large -- it's
-intended as a means to develop a complete EFI firmware implementation, so
-it contains much more code than is needed to develop standalone EFI
-applications. I don't know of any Linux distribution packages for it in
-RPM, Debian package file, or other format; you MUST install the kit from
-source code using its own unusual compilation procedure. The installation
-documentation also omits at least one step and is a bit unclear about
-others. Here's how I installed the toolkit:
-
-1) Download UDK2010.SR1 from
- https://sourceforge.net/apps/mediawiki/tianocore/index.php?title=UDK2010.
-
-2) Type "mkdir /usr/local/UDK2010". You can use another directory, but the
- Makefile for rEFInd's EFI drivers assumes this location. You'll need to
- edit the EDK2BASE line in the Make.common file if you install somewhere
- else.
-
-3) Type "cd /usr/local/UDK2010".
-
-3) Unzip the downloaded file (UDK2010.SR1.Complete.MyWorkSpace.zip) in the
- current directory (/usr/local/UDK2010). This creates a handful of files,
- including a tarball and a couple of .zip files.
-
-4) Type "unzip UDK2010.SR1.MyWorkSpace.zip". This extracts the
+If you're using Linux, GNU-EFI is the easiest way to compile rEFInd. I
+don't describe GNU-EFI's setup here because it's likely to be fairly easy.
+If your distribution provides a recent enough version, you should be able
+to install a package called gnu-efi and be done with it. If not, you'll
+need to download the source code tarball, build it, and install it. This
+process is fairly typical of Linux packages. Read the GNU-EFI documentation
+if you need help. If you're using GNU-EFI, you can skip the rest of this
+section.
+
+You might want to use the TianoCore toolkit if you have problems with
+GNU-EFI or if you want to build rEFInd on a non-Linux platform.
+Unfortunately, the TianoCore toolkit is weird by Linux programming
+standards. It's also quite large -- it's intended as a means to develop a
+complete EFI firmware implementation, so it contains much more code than is
+needed to develop standalone EFI applications. I don't know of any Linux
+distribution packages for it in RPM, Debian package file, or other formats;
+you MUST install the kit from source code using its own unusual compilation
+procedure. The installation documentation also omits at least one step and
+is a bit unclear about others. Here's how I installed the toolkit:
+
+1) Download UDK2014.SR1.UP1.P1 from
+ https://sourceforge.net/apps/mediawiki/tianocore/index.php?title=UDK2014.
+ Note that UDK2015 is now available, but I have not yet adapted rEFInd to
+ build with it. (UDK2015 has made changes that require matching changes
+ to rEFInd.)
+
+2) Type "mkdir /usr/local/UDK2014". You can use another directory, but the
+ rEFInd Makefile assumes this location. You'll need to edit the EDK2BASE
+ variable in the top-level Makefile if you install somewhere else.
+
+3) Type "cd /usr/local/UDK2014".
+
+4) Unzip the downloaded file (UDK2014.SR1.UP1.P1.Complete.MyWorkSpace.zip)
+ in the current directory (/usr/local/UDK2014). This creates a handful of
+ files, including a tarball and a couple of .zip files.
+
+5) Type "unzip UDK2014.SR1.UP1.MyWorkSpace.zip". This extracts the