aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/.github (unfollow)
Commit message (Collapse)Author
2021-04-13project.ci: add --hint parameterEgor Tensin
This is a stupid workaround for testing other CI systems on GitHub Actions.
2021-04-13remove excessive logging & obsolete project.ci.* packagesEgor Tensin
Logging command line arguments before parsing them is a bit excessive.
2021-04-13tools: drop the .py extensionEgor Tensin
2021-04-13workflows/basic: add job for publishing to PyPIEgor Tensin
2021-04-05workflows/basic: call clang-format.pyEgor Tensin
2021-03-24project.ci: use same variable names for all CIsEgor Tensin
Using different ones was quite weird to begin with.
2021-03-24project.ci: change build directoryEgor Tensin
It's now <source directory>/../build for consistency.
2021-03-20workflows: fail-fastEgor Tensin
They are stable enough.
2021-03-19workflows/basic: enable on windows-2016Egor Tensin
2021-03-14workflows/ci_appveyor: create C:\projects before cachingEgor Tensin
2021-03-14workflows: _really_ fix Boost caching?..Egor Tensin
actions/cache@v2 doesn't work on windows-2016 images, since those contain the GNU tar, which cannot work with \ as path separator. This was fixed in package @actions/cache v1.0.5, which is used by action actions/cache@v2.1.4 [1][2]. In addition, it simply couldn't find tar.exe on those images thanks to my action cleanup-path, which removed the corresponding directory (I think it was Git's bin/) from PATH. It worked for windows-2019 images thanks to them containing tar.exe in System32. Solved by turning cleanup-path into a JavaScript action with a "post" step, which restores the original PATH value. [1]: https://github.com/actions/virtual-environments/issues/480 [2]: https://github.com/actions/toolkit/issues/632
2021-03-13project.ci: cache Boost downloadsEgor Tensin
2021-03-13workflows: fix Boost cachingEgor Tensin
It seemingly doesn't work unless the key includes runner.os?
2021-03-13workflows: cache Boost downloadsEgor Tensin
2021-01-25project.ci: auto-fill --toolset from environmentEgor Tensin
2021-01-25project.ci: auto-detect CI systemEgor Tensin
2021-01-19bye-bye, Travis & AppVeyor!no_more_travisEgor Tensin
2021-01-18project.ci: add GitHub ActionsEgor Tensin
2021-01-18project.ci: --install picks the directory automaticallyEgor Tensin
2021-01-18workflows: add Travis/AppVeyor simulationsEgor Tensin
2021-01-18workflows: add "Basic usage"Egor Tensin
2021-01-18workflows: mask the less interesting onesEgor Tensin
2021-01-17workflows: check if Travis/AppVeyor are brokenEgor Tensin
2021-01-17GIANT CLUSTERFUCK OF A COMMITEgor Tensin
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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-15 05:00:14 +0000