* The gnu-efi library is used for convenience
* Also use the Hello World example from
  http://wiki.osdev.org/User:Jnc100/UEFI_Bare_Bones

* Must use MinGW-w64 to compile libefi

* Now isn't _THAT_ nice! ;)

* Use a vbscript for automatic download of the OVMF firmware
* Also fix unwanted references to ia64 in gnu-efi

* also update comment from patch

* Also optimize release for size

* Add HTTP call and make other calls more generic

* Close QEMU on program exit (EFI shutdown)
* Check for QEMU presence and other debug script improvements
* Remove unneeded compilation options and increase warning level

* And remove gnu-efi patch as it now includes our changes

* Also fix the entrypoint label

* As per https://msdn.microsoft.com/en-us/library/abx4dbyh.aspx, libcmt has been
  broken down in multiple libraries, which must be included for Debug compilation,
  else you get symbols not found errors.

* NB: gnu-efi's 4091 warnings have been unsilenced as we sent a patch to the
  library authors to fix it there, and we'll update our ref once applied.

* This fixes a bunch of VS 2015 warnings

* Since SourceForge are being such ASSES about direct downloads...

* Update gnu-efi to latest for ARM
* Fixes for IA32

* This should fix MinGW32 compilation

* Required for the next commit

* When compiled with various checks, Visual Studio includes code to
  forcefully terminate the process if a check fails. It seems that this code
  depends on Kernel32.dll, resulting in invalid imports in Dependency
  Walker (SUBSYSTEM_EFI binaries should not depend on SUBSYSTEM_WIN32 DLLs),
  as well in validation errors when Secure Boot is involved.
* This commit removes this as well as all library dependencies for x86.
* A dependency to libcmt/libcmtd is still kept for ARM, due to missing
  mathematical calls, but this isn't expected to cause dependencies issues.
* Closes #4

* Optimizing for size may result in attempting to link with memset()

* Also simplify the definition of $(IntDir)

* All things considered, it is likely that users of uefi-simple
  may run into situations where they need some of the mathematical
  functions provided by libcmt (as is the case with efifs), so add
  it back for good measure on x86_32 and x86_64.
* Also further simplify additional library directories definition

* Also update gnu-efi to latest

* Also reduce the size of MinGW binaries

* gnu-efi's crt0 requires the use of 'efi_main' as the entrypoint

* Closes #5

* -device VGA enables you graphic output on ARM, but then the keyboard
  input does not work, and I'm not sure whether the issue is with the
  Linaro QEMU_EFI.fd firmware or QEMU itself.
* By removing the VGA option and disabling all devices but serial, we
  force QEMU to default to serial, where keyboard input works.

* ia32, x64 and arm

* Note that the Clang version is set to use GCC extensions (not MSVC ones)

* Also add -fno-builtin to Clang options (though that doesn't seem to do anything with C2/Clang)

* Less CPU intensive than a loop

* Also update gnu-efi to latest

* Visual Studio ARM compilation is now only supported with Clang
  (through a CRT that we had to craft ourselves - thanks Microsoft!!)

* The default for QEMU is to mount -hd# virtual images as read-only. This does not appear
  to be an issue on Linux, and, up to 2.8, wasn't an issue on Windows either, but ever
  since version 2.9, the Windows binary images seems to have been compiled with a
  requirement to save the Non-volative environmental variables to the ESP by default. Of
  course, this means that, unless you add the 'rw' option to '-hda fat:image', QEMU will
  not start...
* Thanks go to jjolig for the workaround
* Closes #8
* Closes #9

* Requires Update 15.4 and Windows SDK 10.0.16299.0 or later
* Also add /Oi- option to disable intrinsics
* Closes #7

* Needed to have proper uint64_t size on ARM64
* Also add /Oi- option to MSVC project files

* Since Microsoft are dropping it...

* Also update gnu-efi to latest and use HTTPS downloads

* Prevents warning C4244 during compilation

* Also update gnu-efi to latest

* Also update gnu-efi to latest

* Also update README

This can be useful if you installed your own keys for Secure Boot.

With the latest gnu-efi, it is no longer necessary to add specific
macros or additional directories in the includes path.

* Also use our own fork of gnu-efi.