glib/.gitlab-ci/test-msvc.bat

@echo on
:: vcvarsall.bat sets various env vars like PATH, INCLUDE, LIB, LIBPATH for the
:: specified build architecture
call "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vcvarsall.bat" x64

:: Remove quotes from script args
setlocal enabledelayedexpansion
set args=
for %%x in (%*) do (
  set args=!args! %%~x
)
set args=%args:~1%

:: FIXME: make warnings fatal
pip3 install --upgrade --user meson==1.4.2 || goto :error
meson setup %args% _build || goto :error
meson compile -C _build || goto :error

meson test -v -C _build --timeout-multiplier %MESON_TEST_TIMEOUT_MULTIPLIER% || goto :error
meson test -v -C _build --timeout-multiplier %MESON_TEST_TIMEOUT_MULTIPLIER% --setup=unstable_tests --suite=failing --suite=flaky

:: FIXME: can we get code coverage support?

goto :EOF
:error
exit /b 1
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed. 2018-05-24 19:18:25 +02:00			`@echo on`
			`:: vcvarsall.bat sets various env vars like PATH, INCLUDE, LIB, LIBPATH for the`
			`:: specified build architecture`
CI: Switch to new Windows runners gitlab will drop cmd.exe support with GitLab 13 so I took the opportunity to add new runners with Windows 2016 and powershell as default. These runners are tagged with win32-ps instead of win32. The old runners will be switched off in the coming weeks. The main difference is that all commands and env expansions use powershell and Windows 2016 instead of 2012r2. 2020-04-29 08:44:43 +02:00			`call "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vcvarsall.bat" x64`
Add Windows native static build using msvc to CI 2022-01-14 17:01:16 +01:00
			`:: Remove quotes from script args`
			`setlocal enabledelayedexpansion`
			`set args=`
			`for %%x in (%*) do (`
			`set args=!args! %%~x`
			`)`
			`set args=%args:~1%`
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed. 2018-05-24 19:18:25 +02:00
			`:: FIXME: make warnings fatal`
build: Bump Meson dependency to 1.4.0 Meson 1.5.1 is available in the fd.o SDK and in Debian testing, so the glib Meson policy says we can update. Update the minimum only as far as 1.4.0 because we don't yet have a need for 1.5.0. This allows us to: - Use file.full_path() to avoid deprecation warnings on str.format(file). - Set c_std=gnu99,c99 to avoid deprecation warnings with gnu99 on MSVC. Update all the CI builds to use the latest 1.4.x patch release, 1.4.2. The FreeBSD runner cannot be updated via `gitlab-ci.yml`, so will be broken for now. Similarly, the macOS build will not work unless `-Dc_std=gnu99` is specified at configure time, due to https://github.com/mesonbuild/meson/issues/13639. 2024-09-05 13:31:09 +02:00			`pip3 install --upgrade --user meson==1.4.2 \|\| goto :error`
meson: Use 'meson setup' to configure This removes a deprecation warning when using 'meson' without 'setup'. 2023-08-14 13:24:28 +02:00			`meson setup %args% _build \|\| goto :error`
ci: Use `meson compile` rather than bare `ninja` This makes it more consistent with `meson setup` in the rest of the file. 2023-08-16 13:57:47 +02:00			`meson compile -C _build \|\| goto :error`
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed. 2018-05-24 19:18:25 +02:00
ci: Use verbose output in meson by default Now that we're using TAP parsing, this will show subtest failures in details but without showing any logging error, that we'd still need to parse from actual logs. 2023-01-20 15:41:17 +01:00			`meson test -v -C _build --timeout-multiplier %MESON_TEST_TIMEOUT_MULTIPLIER% \|\| goto :error`
			`meson test -v -C _build --timeout-multiplier %MESON_TEST_TIMEOUT_MULTIPLIER% --setup=unstable_tests --suite=failing --suite=flaky`
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed. 2018-05-24 19:18:25 +02:00
			`:: FIXME: can we get code coverage support?`

			`goto :EOF`
			`:error`
			`exit /b 1`