Arch Linux User Repository

Since this conflicts with extra/ovmf, it would be nice if it deposited the files in the same location so that I didn't have to modify my qemu config. A Simple symbolic link could do the trick, or installation to both locations?

package() {
  install -D -m644 "${srcdir}"/edk2/Build/OvmfX64/RELEASE_${_toolchain_opt}/FV/OVMF_CODE.fd "${pkgdir}"/usr/share/ovmf/ovmf_code_x64.bin
  install -D -m644 "${srcdir}"/edk2/Build/OvmfX64/RELEASE_${_toolchain_opt}/FV/OVMF_VARS.fd "${pkgdir}"/usr/share/ovmf/ovmf_vars_x64.bin
  install -D -m644 "${srcdir}"/edk2/OvmfPkg/License.txt "${pkgdir}"/usr/share/licenses/ovmf/License.txt

  # symlink
  mkdir -p "${pkgdir}"/usr/share/ovmf/x64
  ln -s /usr/share/ovmf/ovmf_code_x64.bin "${pkgdir}"/usr/share/ovmf/x64/OVMF_CODE.fd
  ln -s /usr/share/ovmf/ovmf_vars_x64.bin "${pkgdir}"/usr/share/ovmf/x64/OVMF_VARS.fd

  # or install to 2 spots
  install -D -m644 "${srcdir}"/edk2/Build/OvmfX64/RELEASE_${_toolchain_opt}/FV/OVMF_CODE.fd "${pkgdir}"/usr/share/ovmf/x64/OVMF_CODE.fd
  install -D -m644 "${srcdir}"/edk2/Build/OvmfX64/RELEASE_${_toolchain_opt}/FV/OVMF_VARS.fd "${pkgdir}"/usr/share/ovmf/x64/OVMF_VARS.fd
}

Hmm... The upstream URL points to something that says: "Whoops, we can't find that page"... I'm a bit confused about which of these packages to use for my virtual (Windows 10) machine:

aur/edk2-ovmf 20180815-1 (+9 0.01%) (Out-of-date 2019-05-23) 
   EDK2 ovmf firmware from Fedora 29 rpm
aur/ovmf-git 1:r25361.514c55c185-1 (+31 0.00%) (Installed: 1:r25460.83463154af-1)
   Tianocore UEFI firmware for qemu.
extra/ovmf 1:r25737.89910a39dc-1 (1.3 MiB 2.0 MiB) 
   Tianocore UEFI firmware for qemu.

I previously used aur/edk2-ovmf, but now it says out-of-date since about a month ago, so I'm wondering if I should just use ovmf-git and if that's safe (I have the impression that extra/ovmf is too old)...? Anyway, I would have no doubts continuing to use edk2-ovmf, if it wasn't flagged as out-of-date, for the past month...

markzz: thank you very much :)

JuniorJPDJ: Updated to fix this. In the future, if there's an issue with the build like this, please flag the PKGBUILD as out-of-date so that it will be apparent when I log into the AUR interface.

@assimilat thanks, it fixes build for me

@markzz can you add this to PKGBUILD?

JuniorJPDJ- fixed the "error 000E: File/directory not found in workspace" error by adding this to the end of the prepare funct:

cd "${srcdir}/edk2"
git submodule update --init --recursive

The package stopped building for me a while ago.

The error I'm getting:

----------------------------------------------------------------------
Ran 262 tests in 1.688s

OK
make[1]: Leaving directory '/home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/BaseTools/Tests'
make: Leaving directory '/home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/BaseTools'
WORKSPACE: /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2
EDK_TOOLS_PATH: /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/BaseTools
CONF_PATH: /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/Conf
Copying $EDK_TOOLS_PATH/Conf/build_rule.template
     to /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/Conf/build_rule.txt
Copying $EDK_TOOLS_PATH/Conf/tools_def.template
     to /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/Conf/tools_def.txt
Copying $EDK_TOOLS_PATH/Conf/target.template
     to /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/Conf/target.txt
Build environment: Linux-4.19.2-arch1-1-ARCH-x86_64-with-glibc2.2.5
Build start time: 22:57:04, Nov.25 2018

WORKSPACE        = /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2
ECP_SOURCE       = /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/EdkCompatibilityPkg
EDK_SOURCE       = /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/EdkCompatibilityPkg
EFI_SOURCE       = /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/BaseTools
CONF_PATH        = /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/Conf


Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = GCC5

Active Platform          = /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/OvmfPkg/OvmfPkgX64.dsc
Flash Image Definition   = /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/OvmfPkg/OvmfPkgX64.fdf

Processing meta-data ......

build.py...
/home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf(31): error 000E: File/directory not found in workspace
        /home/juniorjpdj/.cache/yay/ovmf-git/src/edk2/CryptoPkg/Library/OpensslLib/openssl/e_os.h


- Failed -
Build end time: 22:57:12, Nov.25 2018
Build total time: 00:00:07

HCF: You don't need it. Read the wiki.

I redid the PKGBUILD to closely resemble the one on the official repositories. The only change is the branch. This is why the directories changed and the ovmf_x64.bin file is no longer packaged. If you want the file back, you can modify the PKGBUILD to your liking.

The newest commit doesn't work without modifications.

FYI: Paths have changed from '/usr/share/ovmf/x64/' to '/usr/share/ovmf/'

==========

Problem: ovmf_x64.bin is not specified in PKGBUILD and thus does not get installed/compiled

Solution: Add 'install -D -m644 "${srcdir}"/edk2/Build/OvmfX64/RELEASE_${_toolchain_opt}/FV/OVMF.fd "${pkgdir}"/usr/share/ovmf/ovmf_x64.bin' before line 58 in PKGBUILD.

FYI - Build is failing using openssl-1.1.0e. Changing it to use openssl-1.1.0g fixes it for me, so I believe they've included support for the newer version.