libgnome-volume-control/.gitlab-ci.yml

stages:
- test

build-fedora:
  image: fedora:latest
  stage: test
  before_script:
    - dnf install -y redhat-rpm-config gcc clang meson pulseaudio-libs-devel alsa-lib-devel gtk3-devel
  script:
    - cd .gitlab-ci
    - meson _build
    - ninja -C _build
    - rm -rf _build
    - CC=clang meson _build
    - ninja -C _build
ci: Add CI This just builds the "what-did-you-plugin" test application, but it's good enough to catch the worst failures. 2019-02-27 08:20:31 -05:00			`stages:`
			`- test`

			`build-fedora:`
			`image: fedora:latest`
			`stage: test`
			`before_script:`
ci: Build with clang as well 2023-07-18 10:28:32 -04:00			`- dnf install -y redhat-rpm-config gcc clang meson pulseaudio-libs-devel alsa-lib-devel gtk3-devel`
ci: Add CI This just builds the "what-did-you-plugin" test application, but it's good enough to catch the worst failures. 2019-02-27 08:20:31 -05:00			`script:`
ci: Use meson for CI build All consumers of the submodule switched to meson, except the CI build. It neither seems useful to maintain a second build system just for that purpose, nor to test a configuation that isn't used by anybody. So set up a small fake project that includes gvc as a subproject, and build that during CI. https://gitlab.gnome.org/GNOME/libgnome-volume-control/merge_requests/9 2019-11-22 13:34:06 -05:00			`- cd .gitlab-ci`
			`- meson _build`
			`- ninja -C _build`
ci: Build with clang as well 2023-07-18 10:28:32 -04:00			`- rm -rf _build`
			`- CC=clang meson _build`
			`- ninja -C _build`
ci: Add CI This just builds the "what-did-you-plugin" test application, but it's good enough to catch the worst failures. 2019-02-27 08:20:31 -05:00