luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-01-12 15:36:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

ci: Re-enable fatal warnings for FreeBSD CI

Browse Source 
Now that the CI runner has Meson 1.4, we can revert commit
eda5bb386b and re-enable fatal warnings.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>
This commit is contained in:
Philip Withnall 2024-09-26 13:29:52 +01:00
parent c2a5bd2c65
commit 1f59e89391
No known key found for this signature in database
GPG Key ID: DCDF5885B1F3ED73
1 changed files with 1 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
.gitlab-ci.yml
View File

@ -656,14 +656,7 @@ freebsd-13-x86_64:
before_script: before_script:
- bash .gitlab-ci/show-execution-environment.sh - bash .gitlab-ci/show-execution-environment.sh
script: script:
# FIXME: We can’t use ${MESON_COMMON_OPTIONS} here because the FreeBSD 13 - meson setup ${MESON_COMMON_OPTIONS}
# runner has Meson 1.3 installed. This has an API hole where previous
# methods of getting paths from files() objects are rejected as deprecated,
# but no replacements are available. Hence, we can’t build with
# --fatal-meson-warnings. This should be fixed in Meson 1.4. It’s also fine
# with Meson 1.2.3 (which is what we use on all the other CI runners).
# See https://github.com/GNOME/glib/commit/71061fdcb33b8c26f5f8467cb3ac10704d65c87d
- meson setup --buildtype debug --wrap-mode=nodownload
--localstatedir=/var --localstatedir=/var
-Db_lundef=false -Db_lundef=false
-Dxattr=false -Dxattr=false