Full CMake build support for all Msys64 sub-systems, with optonal vcpkg integration.
Currently being developed in tandem with my specialized fork of MSYS2-Pacman, with the aim of bringing the building of package binaries from hosted source repositories to msys2 environments for Windows.
As a means of thoroughly testing the toolchains, I have simultaneously developed several small projects that require a more extensive usage of the libraries and headers available in each subsystem; A simple CMake application suitable for templating new projects, a specialized fork of MSYS2-Pacman for package management, and a native windowed application using the Win32 API and Direct2D graphics.
Simply pass the scripts/buildsystems/MSYS2.cmake file as your "CMAKE_TOOLCHAIN_FILE", along with a desired "MSYSTEM".
$ cmake -S "<path/to/project>" -B "<path/to/project>/build" "-DMSYSTEM=MINGW64" "-DCMAKE_TOOLCHAIN_FILE=<path/to/this/repo>/scripts/buildsystems/MSYS2.cmake" "-DCMAKE_MODULE_PATH=<path/to/this/repo>/scripts/cmake/Modules" -G "Ninja Multi-Config"
Choose an "MSYSTEM" from one of the following options:
- UCRT64
- MINGW64
- MINGW32
- CLANG64
- CLANG32
- CLANGARM64
- MSYS2
IMPORTANT - Make sure you include this part of the above command, to enable the 'MSYSTEM' platform for CMake:
-DCMAKE_MODULE_PATH=<path/to/this/repo>/scripts/cmake/Modules"
- Windows Host machine
- MSYS2 installation (please try to use the default install location)
- CMake
Note that will need to have run the standard init commands for Msys development;
pacman -Syuu
pacman -S --needed base-devel
pacman -S cmake
pacman -S autotools
pacman -S ming-w64-{msystem}-{arch}-toolchain
pacman -S ming-w64-{msystem}-{arch}-cmake
pacman -S ming-w64-{msystem}-{arch}-toolchain
pacman -S ming-w64-{msystem}-{arch}-autotools
Corresponding to the chosen MSYSTEM in order to have the toolchain installed and available to for use by this project. See the MSYS2 (and Packages page) docs for more.
This independent project is an ongoing investigation into the potential of cross-pollinating MSYS2's multi-verse of build envinronments and toolchains, with the source code package registry access and management of Microsoft's vcpkg, thanks to the power and flexibility of CMake.
Fortunately, for this project to achieve it's targets, much of the required configurations are already available within a standard CMake, Msys64, and optionally vcpkg, installation; we have simply defined an additional set of standard processes for directing the flow of file-hopping that CMake does under the hood when configuring/building/etc to pick up combinations of native CMake files that otherwise wouldn't be specified together, using the provided configs alone.
Doing this involves porting the contents of several configuration as found in Windows MSYS2 installations:
(*for "MSYS2")
(**for "MINGW32/64", "CLANG32/64/ARM64", and "URCRT64")
These files are typically used to drive configurations for "PKGBUILD", which is the integrated package-building/bundling mechanism used by 'pacman' in typical development scenarios when using MSYS2.
This project aims to port as much of the above as possible to a natively-CMake-driven process, including the integration of a port Microsoft's 'vcpkg' package manager and its' useful "triplet/toolchain/buildsystem" paradigm:
- Known configuration of system to build software on, i.e., the 'host'*.
- Desired configuration of system to run software on, i.e., the 'target'*.
- Chain of tools to build with, i.e., a 'toolchain'.
- A building process invoking all of the above, i.e., a 'build system'.
*each of these configurations are referred to as 'triplets'
In a CMake-driven build environment, these settings can all be pre-defined with configuration scripts ('toolchain files') which configure CMake with a full set of environment variables, binary/library paths, and compiler flags for each of the available invoking MSYS sub-systems (often known as "MSYSTEM"'s), appropriately setting each of the underlying build tool behaviours for each sub-system, enabling CMake to correctly find and use them.
This project does precisely the above with as minimal user requirements as possible. With the desired toolchain(s) on your pacman-driven Msys installation in place, it should be as simple as passing the 'MSYS2.cmake' buildsystem file (as the CMake toolchain) and an 'MSYSTEM' to your CMake invocation, making the entire sub-system readily available to your CMake/Msys64 projects.
Here's what building with each of the sub-systems offers, as per the MSYS2 documentation:
- MinGW-based x64-bit environment
- GNU compilers and binary utlilities
- 'MSVCRT' C Standard Library
- 'libstdc++' C++ Standard Library
- MinGW-based x32-bit environment
- GNU compilers and binary utlilities
- 'MSVCRT' C Standard Library
- 'libstdc++' C++ Standard Library
- MinGW-based x64-bit environment
- Clang compilers and LLVM binary utlilities
- 'UCRT' C Standard Library
- 'libc++' C++ Standard Library
- MinGW-based x32-bit environment
- Clang compilers and LLVM binary utlilities
- 'UCRT' C Standard Library
- 'libc++' C++ Standard Library
- MinGW-based x64-bit environment
- Support for both GNU and Clang compiler toolchains
- 'UCRT' C Standard Library
- 'libstdc++' C++ Standard Library
- Cygwin-based native environment
- Support for both GNU and Clang compiler toolchains
- 'Cygwin' C Standard Library with 'MSYS2' Runtimes
- 'libstdc++' C++ Standard Library
* Microsoft Visual C++ Runtime (MSVCRT)
** Universal C Runtime (UCRT)
To use the toolchain and buildsystem, first install your MSYSTEM toolchain using pacman as usual, then pass these vars to your CMake invocation when building;
-
"-DCMAKE_TOOLCHAIN_FILE=<path/to/this/repo>/scripts/buildsystem/MSYS2.cmake"
-
"-DMSYSTEM=MINGW64"
-
"-DCMAKE_MODULE_PATH=<path/to/this/repo>/scripts/cmake/Modules"
or, to use a sub-system without the encasing buildsystem, just pass it in as the toolchain file directly (this omits usage as a package manager, but still provides a full configured toolchain and utilities);
- -DCMAKE_TOOLCHAIN_FILE="<path/to/this/repo>/scripts/toolchains/MINGW64.cmake"
* you may of course swap 'MINGW64' for any of the other available MSYSTEM's - just don't forget to include files indicated in the module path as above. CMake will fail without this!
The 'chainload' toolchain files ('scripts/toolchains') are named identically to the chosen "MSYSTEM" and may provide more thorough default behaviours for invoked "MSYSTEM" settings. Use in tandem for best results. However, there is some experimental support for passing just the 'buildsystem' file without any '<MSYSTEM>':
- -DCMAKE_TOOLCHAIN_FILE:FILEPATH="<path/to/this/repo>/scripts/buildsystem/MSYS2.cmake"
"CMAKE_TOOLCHAIN_FILE" and "MSYSTEM" can often also be set in your IDE's CMake integration extension's settings, and/or a 'CMakePresets.json' in the project root folder.
For best results, it is recommended to use either 'Ninja' or 'Ninja Multi-Config' as a generator, with the 'preferred' generator set to one of the Makefile generators - 'Unix/MinGW/MSYS Makefiles' etc.
We have a working implementation of Msys64's 'path type' switching option under the custom CMake variable "MSYS2_PATH_TYPE", as follows:
- "-DMSYS2_PATH_TYPE=inherit"
Inherit the Windows environment's "PATH" variable. Note that this will make all of the Windows path available in current shell, with possible interference in project builds.
- "-DMSYS2_PATH_TYPE=minimal"
Provides a minimal set of paths from the Windows environment's system folder; notably, this excludes all of your Windows 'Program Files' directories.
- "-DMSYS2_PATH_TYPE=strict"
Do not inherit any paths from the Windows environment, and allow for full customization of external paths. This is supposed to be used in special cases such as debugging without need to change this file, but not daily usage.
If set to 'ON', the paths under the current 'MSYSTEM' directory will be scanned before the '<msysRoot>/usr' directory during CMake's file/program/lib lookup routines.
Accepts a Boolean value. Defaults to "ON".
If set to 'ON', the paths under the calling environment's 'PATH' variable will be scanned before any other paths, during CMake's file/program/lib lookup routines.
Accepts a Boolean value. Defaults to "OFF".
Adds '<msystemRoot>/include/X11' to 'CMAKE_SYSTEM_INCLUDE_PATH', and '<msystemRoot>/lib/X11' 'to CMAKE_SYSTEM_LIBRARY_PATH' for lookup.
Accepts a Boolean value. Defaults to "OFF".
Also very much worth noting is that several sub-systems offer "DSX-compatibility" GNU Bin Utils, located various differently-named directories here and there. It seems at least a fun idea to leverage a cmake_option(OPTION_USE_DSX_BINUTILS) or similar, which likewise would favour these directories during file lookups for the tools in question. Again, this is actually all pretty much made possible, in fact quite easy, in CMake's design. Currently there are so very many features, permutations, varieties across the entire project that this concept hasn't yet been explored further, but stay tuned.
This Git repo, named "MSYS2-toolchain", is an independant project, created and maintained by StoneyDSP as a project of interest. By "independant", the author specifies that they have no relation to any of the parties further outlined below in this section of the page.
The below is quoted from https://www.msys2.org/license/
"MSYS2 is a software distribution consisting of several independent parts, each with their own licenses, comparable to a Linux distribution.
The installer, for example, is based on the qt-installer-framework and pre-packs the direct and indirect dependencies of the base meta package. Each package has its own licenses.
The "pacman" package manager in MSYS2 allows users to install other packages available in our repository, each with their own licenses.
The license information for each package as visible on https://packages.msys2.org is maintained on a best effort basis and "we" (quote) make no guarantee that it is accurate or complete."
vcpkg - C++ Library Manager for Windows, Linux, and MacOS
Copyright (c) Microsoft Corporation
vcpkg is distributed under the MIT License
All rights reserved.
CMake - Cross Platform Makefile Generator
Copyright 2000-2023 Kitware, Inc. and Contributors
CMake is distributed under the OSI-approved BSD 3-clause License
All rights reserved.