My MSWIndows build runs on a dedicated virtual (Virtualbox) openSUSE machine. I start the build process with just one call, The host is currently a Mint environment. So it is possible to automatically generate new versions. However "make check" makes no sense. when cross compiling. It takes a long time and only a small part of the checks are Ok.
Maybe it is possible to change "make check" so it only includes the checks which work on the platform it uses or with a parameter to get the same effect. This way for MacOS a few checks are skipped and for MSWindows builds in cross compiling only a few checks are triggered. At least after that it is known which checks can be executed and the issues with the checks for cross compiling can be solved if there is time.
Date: Thu, 30 Jul 2020 08:53:29 +0200
From: Friedrich Beckmann <firstname.lastname@example.org>
To: Ben Pfaff <email@example.com>
Cc: pspp-dev <firstname.lastname@example.org>
Subject: Continuous integration tests also for MacOS and Windows
Message-ID: <5ABF5BD6-538F-4138-9E51-27171CEFB183@gmx.de" target="_blank">5ABF5BD6-538F-4138-9E51-27171CEFB183@gmx.de>
Content-Type: text/plain; charset=utf-8
sure - it would be nice to have CI for MacOS and Windows too. I do my pspp development on my Macbook laptop and I do not have a „networked“ Mac somewhere. As Jeremy mentioned macports uses travis-ci - I am not sure if they run „make check“ during the test build. For MacOS there are two ways to install pspp
a) via macports
b) via install bundle
It tried to describe the differences here: https://www.hs-augsburg.de/homes/beckmanf/pspp/ „Technology and Build process“
The main obstacle for macports is that you need to install an Apple XCode Compiler and the macports environment before you can install pspp.
If I remember correctly Harry builds the windows version as a cross compile from linux and the test suite does not run on Windows.