luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-07 01:46:16 +01:00
Code Issues Packages Projects Releases Wiki Activity
85d8a618ad
glib/.gitlab-ci/test-msvc.bat

62 lines
2.2 KiB
Batchfile
Raw Normal View History

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
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=
CI: Use Visual Studio 2019 for the MSVC CI ...and add ability to select target platform for calling vcvarsall.bat, so that we can accomodate 32-bit builds and possibly ARM64 builds in the CI if we need to.
2024-09-30 12:08:15 +02:00
set stash_plat=0
Add Windows native static build using msvc to CI
2022-01-14 17:01:16 +01:00
for %%x in (%*) do (
CI: Use Visual Studio 2019 for the MSVC CI ...and add ability to select target platform for calling vcvarsall.bat, so that we can accomodate 32-bit builds and possibly ARM64 builds in the CI if we need to.
2024-09-30 12:08:15 +02:00
if "%%x" == "--plat" set stash_plat=1
if "!stash_plat!" == "0" set args=!args! %%~x
CI: Add a 32-bit Visual Studio 2019 config This way, we can continue to test whether 32-bit builds continue to work with Visual Studio builds. Note that this uses the x64-to-x86 cross compiler.
2024-10-01 10:25:45 +02:00
if "!stash_plat!" == "1" if /i not "%%x" == "--plat" (set plat=%%x) & (set stash_plat=0)
Add Windows native static build using msvc to CI
2022-01-14 17:01:16 +01:00
)
set args=%args:~1%
CI: Use Visual Studio 2019 for the MSVC CI ...and add ability to select target platform for calling vcvarsall.bat, so that we can accomodate 32-bit builds and possibly ARM64 builds in the CI if we need to.
2024-09-30 12:08:15 +02:00
if "!plat!" == "" set plat=x64
:: vcvarsall.bat sets various env vars like PATH, INCLUDE, LIB, LIBPATH for the
:: specified build architecture
call "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Auxiliary\Build\vcvarsall.bat" !plat!
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed.
2018-05-24 19:18:25 +02:00
CI: Add CI job for VS2019 ARM64 builds We need to write a Meson cross-compilation file on the fly here, hence the additions in test-msvc.bat to set up the paths. Like the 32-bit VS2019 CI job this is only run manually or weekly.
2024-10-04 06:54:51 +02:00
:: Setup and write a cross-compilation file for ARM64 builds
if not "!plat!" == "x64_arm64" goto :continue_build
set cross_file=vs2019-arm64.txt
echo [host_machine]>!cross_file!
echo system = 'windows'>>!cross_file!
echo cpu_family = 'aarch64'>>!cross_file!
echo cpu = 'arm64'>>!cross_file!
echo endian = 'little'>>!cross_file!
echo.>>!cross_file!
echo [binaries]>>!cross_file!
echo c = 'cl'>>!cross_file!
echo cpp = 'cl'>>!cross_file!
echo c_ld = 'link'>>!cross_file!
echo cpp_ld = 'link'>>!cross_file!
echo ar = 'lib'>>!cross_file!
echo windres = 'rc'>>!cross_file!
echo.>>!cross_file!
echo [properties]>>!cross_file!
echo skip_sanity_check = true>>!cross_file!
set args=%args% --cross-file=!cross_file!
:continue_build
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: Skip PCRE2 tests for 32-bit Visual Studio builds ...in the main tests that we expect to pass. Due to an upstream issue in PCRE2-10.44, disable running the PCRE2 tests for now, until the next release (or so) of PCRE2, as the issue has already been resolved in upstream PCRE2 but has not made it to the PCRE2 release that we use for our subprojects.
2024-10-04 06:54:51 +02:00
:: FIXME: Skip PCRE2 tests for now for 32-bit x86 builds, until we pull in pcre2-10.45 (or so)
:: from our subprojects, as 32-bit Windows Visual Studio tests are fixed upstream
:: Upstream PRs:
:: https://github.com/PCRE2Project/pcre2/pull/480
:: https://github.com/PCRE2Project/pcre2/pull/468
if "!plat!" == "x64_x86" meson test -v -C _build --timeout-multiplier %MESON_TEST_TIMEOUT_MULTIPLIER% --no-suite pcre2 || goto :error
if not "!plat!" == "x64_x86" meson test -v -C _build --timeout-multiplier %MESON_TEST_TIMEOUT_MULTIPLIER% || goto :error
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% --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?
CI: Add CI job for VS2019 ARM64 builds We need to write a Meson cross-compilation file on the fly here, hence the additions in test-msvc.bat to set up the paths. Like the 32-bit VS2019 CI job this is only run manually or weekly.
2024-10-04 06:54:51 +02:00
if not "!cross_file!" == "" if exist !cross_file! del /f/q !cross_file!
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed.
2018-05-24 19:18:25 +02:00
goto :EOF
:error
exit /b 1
Reference in New Issue Copy Permalink