Skip to content

How to setup a new Repo for a Platform that will use Project MU

This document will describe the base guidelines for setting up a Project MU repo.

  1. You will need to install the prerequisites tools
  2. Determine how to layout your project and the content
    • Look at layout to understand our recommended repository layout.
    • You can also look at ms-iot iMX8 for a real platform implementation.
    • Check out our docs in our Project Mu Teams channel as we have presentations on OVMF and Intel OpenKBL platforms.


I will use the term workspace root to reference the base folder for your code tree.

Ordinarily, we use the Platform Repository as the outer-most layer. This means that the outermost git repository is where we store Platform specific files and libraries. In this case, our Platform Repo is also our workspace root. If you choose to have a different repository layout, it will be important to note what your workspace root is, as it should still be the base folder of your code tree.

Submodules are full git repos on their own. What we do with these repos is add them as sub-repos to the workspace root. Git will create a .gitmodules file that contains links to the repo and default branches. There are git submodule commands that you can use to work with your submodules, such as:

git submodule add <url> <path>  # url to submodule, path to submodule installation
git submodule update --init --recursive  # Recursively initializes and updates all submodules.
git submodule foreach git status  # git submodule foreach can be used to run a command in each submodule.
                                  # git status is just an example.

For more information available here.

Create Git Repo

Make new directory.

mkdir NewPlatformRepo
cd NewPlatformRepo
git init

This will serve as our Platform Repository as well as our Workspace Root.

For more information on creating a Git repo, here are command line instructions and here are web instructions.

Add pertinent submodules

Project MU is separated into submodules. For each submodule that you need for your project, run the "git submodule add" command to add it to your base Repository. The path after the URL is the path we typically use to group the submodules. You can change it if you'd like, just remember your environment will diverge from the one in these instructions.


This is the core section of TianoCore. Contains the guts of UEFI, forked from TianoCore, as well as the BaseTools needed to build. You will need this to continue.

git submodule add MU_BASECORE


Additional, optional libraries and tools we've added to make MU great!

git submodule add Common/MU


Additional, optional libraries and tools forked from TianoCore.

git submodule add Common/TIANO


This module is a sample implementation of a FrontPage and several BDS support libraries. This module is intended to be forked and customized.

git submodule add Common/MU_OEM_SAMPLE


Silicon code from TianoCore has been broken out into individual submodules. This is the ARM specific submodule.

git submodule add Silicon/ARM/TIANO


Silicon code from TianoCore has been broken out into individual submodules. This is the Intel specific submodule.

git submodule add Silicon/INTEL/TIANO

You can run git submodule --update --init to make sure all the submodules are set up.

Adding your platform contents

├── Common/
│   └── ...                    # MU_PLUS, MU_OEM_SAMPLE, MU_TIANO_PLUS are generally created by the "git submodule ..."
├── PlatformGroup/
│   └── PlatformName/
│       └──   # Python script to provide information to the build process.
│       └── Platform.dsc       # List of UEFI libraries and drivers to compile, as well as platform settings.
│       └── Platform.fdf       # List of UEFI Drivers to put into Firmware Volumes.
├── Silicon/
│   └── SiProvider/            # You should create a separate git repo for Silicon code for development with partners.
│       └── REF_CODE/          # Enablement code for your architecture
├── .gitattributes
├── .gitignore
└── .gitmodules

You will need to create, Platform.dsc, and Platform.fdf. These files will go inside the platform folder, which will be New_Platform_Repo/PlatformGroup/PlatformName. The ms-iot iMX8 repo can help you get started as a layout reference and can demonstrate the PlatformBuild file. More information about PlatformBuild can be found here.