This page provides step-by-step instructions or setting up a EDK II build environment on Windows systems.

GitHub (https://help.github.com/index.html) provides step-by-step instructions for user registration and basic features supported by GitHub.

• Git for Windows OS is available at: (http://git-scm.com/download/win)
• TortoiseGit for windows OS is available at (https://tortoisegit.org/download/)

• The EDK II project repository is available at https://github.com/tianocore/edk2.
• Prebuilt Windows tools are available at https://github.com/tianocore/edk2-BaseTools-win32.
• Please note that FatPkg is not included in the EDKII project repository, it is an independent repository which can be found at https://github.com/tianocore/edk2-FatPkg.
  
  

Content that is not released under an accepted open source license can be found at https://github.com/tianocore/edk2-non-osi.

If your network utilizes a firewall with a web proxy, then you may need to configure your proxy information for various command line applications to work. You may need to consult with your network administrator to find out the computer name and port to use for proxy setup. The following commands are common Git Bash examples of how you would configure your proxy by setting an environment variable:

    $ git config --global https.proxy <proxyname>.domain.com:<port>
    $ git config --global http.proxy <proxyname>.domain.com:<port>

Note: Some of the following examples use the Multiple Workspace feature to configure the EDK II BaseTools. More information on the Multiple Workspace feature can be found at the following location.

• Multiple_Workspace

If you use the command line version, then you can easily checkout the edk2 to the C:\edk2 directory with the following git command: Main repository: https://github.com/tianocore/edk2

    $ git clone https://github.com/tianocore/edk2

• Create a workspace directory
• Change to the workspace directory
• Clone the EDK II project repository
  • git clone https://github.com/tianocore/edk2
• Clone the edk2-BaseTools-win32 repository
  • git clone https://github.com/tianocore/edk2-BaseTools-win32
• Set environment variables:
  • EDK_TOOLS_BIN – Set it as the edk2-BaseTools-win32 directory

Example:

• Inside Git Bash

     $ git clone https://github.com/tianocore/edk2
     $ git clone https://github.com/tianocore/edk2-BaseTools-win32

• Windows CMD prompt:

     C:\edk2> set EDK_TOOLS_BIN=c:\efi\test\edk2-BaseTools-win32

• Change to the edk2 directory
• Run the edksetup.bat script

      C:\edk2> CD efi\test\edk2
      C:\edk2> edksetup

When the above steps are done, the directory structure will look like:

  efi
    └───test (WORKSPACE)
       ├───edk2
       └───edk2-BaseTools-win32

You will need to edit the Conf\target.txt file. First, change the ACTIVE_PLATFORM to the MdeModulePkg:

C:\edk2> notepad Conf\target.txt

ACTIVE_PLATFORM should look like this in Conf\target.txt:

ACTIVE_PLATFORM       = MdeModulePkg/MdeModulePkg.dsc

Modify TOOL_CHAIN_TAG in target.txt for the toolchain installed on your system. There are many options, so review the tools_def.txt to find the appropriate toolchain for your system. Search for 'Supported Tool Chains' in tools_def.txt to see the valid options for TOOL_CHAIN_TAG.

TOOL_CHAIN_TAG        = VS2008x86

See also: Windows-systems-ToolChain-Matrix for how to change the Tool Chain Tag.

Also, consider if you want to build a different processor architecture by changing the TARGET_ARCH value in target.txt. Please consider that certain toolchains only support building certain processor architectures.

Now you should be able to simply run the build command to compile the MdeModulePkg.

C:\edk2> build

As a tangible result of the build, you should have the HelloWorld UEFI application. If you have a UEFI system available to you which matches the processor architecture that you built, then this application should be able to run successfully under the shell.

C:\edk2> dir /s Build\MdeModule\HelloWorld.efi

Once your build environment is set up you might be interested in building the OVMF platform which is included in the main edk2 source tree. Since OVMF builds a full system firmware image this may be of interest to UEFI system firmware developers.

• Getting-Started-Writing-Simple-Application