spicetools/external/cpu_features/cmake/ci
2024-08-28 11:10:34 -04:00
..
doc Initial re-upload of spice2x-24-08-24 2024-08-28 11:10:34 -04:00
docker Initial re-upload of spice2x-24-08-24 2024-08-28 11:10:34 -04:00
sample Initial re-upload of spice2x-24-08-24 2024-08-28 11:10:34 -04:00
vagrant/freebsd Initial re-upload of spice2x-24-08-24 2024-08-28 11:10:34 -04:00
Makefile Initial re-upload of spice2x-24-08-24 2024-08-28 11:10:34 -04:00
README.md Initial re-upload of spice2x-24-08-24 2024-08-28 11:10:34 -04:00

Makefile/Docker testing

To test the build on various distro, we are using docker containers and a Makefile for orchestration.

pros:

  • You are independent of third party CI runner config (e.g. github action virtual-environnments).
  • You can run it locally on your linux system.
  • Most CI provide runners with docker and Makefile installed.

cons:

  • Only GNU/Linux distro supported.

Usage

To get the help simply type:

make

note: you can also use from top directory

make --directory=cmake/ci

Example

For example to test mips32 inside an container:

make mips32_test

Docker layers

Dockerfile is splitted in several stages.

docker

Makefile/Vagrant testing

To test build for FreeBSD we are using Vagrant and VirtualBox box.

This is similar to the docker stuff but use vagrant as docker cli and VirtuaBox to replace the docker engine daemon.