205 Commits

Author	SHA1	Message	Date
Christoph Reiter	e8798a4c22	ci: update meson ... Rebuild the fedora docker image to get the newest meson release and use pip to install the newest version for MSYS2. https://bugzilla.gnome.org/show_bug.cgi?id=795711	2018-05-02 11:09:25 +01:00
Christoph Reiter	97c28f7fe1	ci: fix warnings and enable --werror for the mingw build ... Fix various warnings regarding unused variables, duplicated branches etc by adjusting the ifdeffery and some missing casts. gnulib triggers -Wduplicated-branches in one of the copied files, disable as that just makes updating the code harder. The warning indicating missing features are made none fatal through pragmas. They still show but don't abort the build. https://bugzilla.gnome.org/show_bug.cgi?id=793729	2018-04-25 17:23:50 +02:00
Christoph Reiter	995f75cdd7	gitlab-ci: Add 32bit MinGW jobs using MSYS2 ... This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729	2018-04-25 17:23:49 +02:00
Emmanuele Bassi	19ffd365ff	ci: Install Meson from PyPI ... The base Fedora image we use for our CI does not always have an updated Meson package to fit our requirements. Let's install Meson using Python's pip instead.	2018-03-29 09:57:55 +01:00
Emmanuele Bassi	e04d2e81fc	ci: Add GitLab CI description file ... We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635	2018-02-20 13:49:21 +00:00