aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/.github/actions/check-boost-libraries (follow)
Commit message (Collapse)AuthorAge
* boost: root/ -> install_dir/Egor Tensin2026-03-29
|
* project.boost: switch from `stage` to `install`Egor Tensin2026-01-20
| | | | | | | | | That's part of a global transition aiming to switch to Boost CMake files. Since 1.70.0, they've been releasing CMake files, which I should (?) be using. Additionally, modern CMake versions simply deprecate the FindBoost module (see policy CMP0167), insisting on using the supplied CMake files. I'll try to continue supporting old Boost versions; let's see how it goes.
* GIANT CLUSTERFUCK OF A COMMITEgor Tensin2021-01-17
OK, this is epic. I was basically just trying to a) support Clang and b) add more test coverage. _THREE MONTHS_ and a few hundred CI runs later, this is what I came up with. I don't know how it ended up being what it is, but here we go. Some highlights of the changes: 1) CI builds has been moved to GitHub Actions, 2) the entire notion of a toolchain has been reworked; it now supports Clang on all platforms. * .github: this directory contains the GitHub Actions workflow scripts/actions. In the process, I created like 6 external GitHub actions, but it's still pretty massive. An upside is that it covers much more platform/toolchain combinations _and_ check a lot of the expected post-conditions. TODO: .ci/Makefile is obsolete now, as well as .travis.yml and .appveyor.yml. * common.cmake: added Clang support. In the process, a great deal has been learned about how CMake works; in particular, static runtime support has been reworked to be more robust. * project: the entire notion of a "toolchain" has been reworked. Instead of a measly --mingw parameter, there's now a separate --toolset parameter, which allows you to choose between GCC, Clang, MSVC, etc. Both Boost and CMake build scripts were enhanced greatly to support Clang and other toolchains in a more robust way.