i'm getting started to write a little and simple application with edk2.
So to write a simple edk2 UEFI application , i have started like this :
#git clone https://github.com/tianocore/edk2.git
#. edksetup.sh BaseTools
Loading previous configuration from /media/ledoux/Data/osdev/devos/edk2/edk2/Conf/BuildEnv.sh
WORKSPACE: /media/ledoux/Data/osdev/devos/edk2/edk2
EDK_TOOLS_PATH: /media/ledoux/Data/osdev/devos/edk2/edk2/BaseTools
CONF_PATH: /media/ledoux/Data/osdev/devos/edk2/edk2/Conf
#vi Conf/target.txt
(there , i have put : TARGET_ARCH = IA32 X64 TOOL_CHAIN_TAG = VS2017)
# BUILD -a X64
Build environment: Linux-5.7.0-kali1-amd64-x86_64-with-glibc2.29
Build start time: 08:32:11, Sep.03 2020
WORKSPACE = /media/ledoux/Data/osdev/devos/edk2/edk2
EDK_TOOLS_PATH = /media/ledoux/Data/osdev/devos/edk2/edk2/BaseTools
CONF_PATH = /media/ledoux/Data/osdev/devos/edk2/edk2/Conf
PYTHON_COMMAND = /usr/bin/python3.8
Processing meta-data
Architecture(s) = X64
Build target = DEBUG
Toolchain = VS2017
Active Platform = /media/ledoux/Data/osdev/devos/edk2/edk2/EmulatorPkg/EmulatorPkg.dsc
..................
- Failed -
Build end time: 08:32:29, Sep.03 2020
Build total time: 00:00:18
why the build was failed ?? Is it because the bad repository ?? how can i create OVMF.fd file after build it ???
You're building under Linux, so you don't have Visual Studio (which is what VS2017 refers to). The build system really ought to say something more useful about it, but ... I can confirm from own experiments that it doesn't.
Use a toolchain tag of GCC5 instead - that one is still valid for the latest gcc10 builds.