This commit removes the 'Release' `B_BUILD_TYPE` condition for the Mac
builder, and instead just keeps the condition of the image ONLY to be
built by the Big Sur build agent.
Now, the reason for that condition is because I am future proofing the
CI configuration for when we ship M1 builds. Currently, we do not. The
other reason, but also more pressing, is to avoid multiple artifacts
being published. There *is* a possibility the Big Sur build agent
becomes incompatible with older macOS releases, but the CMake
configuration would seem to suggest there's backwards compatibility
being available.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
This commit merges the macOSRelease job into one unified Mac build job.
Using Azure Pipelines conditionals (AND), we check for the build type being an release, and the build agent being Big Sur.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
This commit changes the CI configuration to dual-build Release and Debug types
for the Mac build agents - Mojave, Catalina and Big Sur. This ensures for a double check on each build type during testing.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
Now, CI builds for macOS involve three separate builds for a range of macOS versions, and a final Universal macOS Binary made on Big Sur. It should work with the M1 chip and x86_64 Intel Macs.
I have also renamed osx_environment->macOS_environment.sh to reflect the new name change of Apple's desktop OS.
In terms of the clean_builds.sh script, this has also been refactored to be more resilient, and efficient (marginally).
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
Azure Pipelines no longer supports Ubuntu 16.04, so to remove the
error, this commit removes it from the cross-platform matrix.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
This is an initial test of building Barrier for multiple macOS versions.
For:
- Big Sur
- Moja\ve
- Catalina
I think there's an indentation issue somewhere, but VS Code isn't
'seeing' it... let's hope this works.
If it does, we can proceed to merge.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
The Azure Pipelines MacOS vmImage has an old version of OpenSSL (1.0.2t)
installed at /usr/local/opt/openssl. Normally with Homebrew this directory
would be linked to the currenly installed version of OpenSSL (1.1.x) in
/usr/local/Cellar, but since it has been installed manually here it interferes
with linking libssl.a and libcrypto.a static libraries which causes the build
to fail.