| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
| |
The weird magic going on in the ci-{boost,build} scripts is honestly too
weird. With hindsight, it seems to me that it's much better to just
build a project with the same command during a CI run as when developing
locally.
Plus, I haven't really used either Travis or AppVeyor in quite some
time, so this code was mostly untested really.
|
| |
|
|
| |
Accordingly, rename ci-cmake to ci-build.
|
| |
|
|
| |
This should speed things up. Hopefully I didn't mess it up.
|
| |
|
|
| |
windows-latest no longer support building older Boost releases.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
The v2 tag was finally bumped to v2.1.5 (I needed v2.1.4).
|
| |
|
|
|
|
|
| |
Forgot to switch to $RUNNER_WORKSPACE/build in the workflows also.
Also, the usual crap with the cache action made me change the cache
keys, or it would be restore in the wrong location for some reason.
|
| |
|
|
| |
Logging command line arguments before parsing them is a bit excessive.
|
| |
|
|
| |
Using different ones was quite weird to begin with.
|
| |
|
|
| |
It's now <source directory>/../build for consistency.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
