tree: 121f5a3f6c792b2a30043070ce99fc98fcf5c6a3 [path history] [tgz]
  1. deqp_runner_run.ps1
  2. Dockerfile_build
  3. Dockerfile_test
  4. Dockerfile_vs
  5. mesa_build.ps1
  6. mesa_container.ps1
  7. mesa_deps_build.ps1
  8. mesa_deps_choco.ps1
  9. mesa_deps_test.ps1
  10. mesa_deps_vs2019.ps1
  11. mesa_vs_init.ps1
  12. piglit_run.ps1
  14. spirv2dxil_check.ps1
  15. spirv2dxil_run.ps1

Native Windows GitLab CI builds

Unlike Linux, Windows cannot reuse the freedesktop ci-templates as they exist as we do not have Podman, Skopeo, or even Docker-in-Docker builds available under Windows.

We still reuse the same model: build a base container with the core operating system and infrequently-changed build dependencies, then execute Mesa builds only inside that base container. This is open-coded in PowerShell scripts.

Base container build

The base container build job executes the mesa_container.ps1 script which reproduces the ci-templates behaviour. It looks for the registry image in the user‘s namespace, and exits if found. If not found, it tries to copy the same image tag from the upstream Mesa repository. If that is not found, the image is rebuilt inside the user’s namespace.

The rebuild executes docker build which calls mesa_deps.ps1 inside the container to fetch and install all build dependencies. This includes Visual Studio Community Edition (downloaded from Microsoft, under the license which allows use by open-source projects), other build tools from Chocolatey, and finally Meson and Python dependencies from PyPI.

This job is executed inside a Windows shell environment directly inside the host, without Docker.

Mesa build

The Mesa build runs inside the base container, executing mesa_build.ps1. This simply compiles Mesa using Meson and Ninja, executing the build and unit tests. Currently, no build artifacts are captured.

Using build scripts locally

*.ps1 scripts for building dockers are using PowerShell 7 to run