| Commit message (Collapse) | Author | Age |
| ... | |
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
In addition, command line arguments have been overhauled for sanity and
consistency.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
egor-tensin/dependabot/github_actions/egor-tensin/cleanup-path-5
build(deps): bump egor-tensin/cleanup-path from 4 to 5
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [egor-tensin/cleanup-path](https://github.com/egor-tensin/cleanup-path) from 4 to 5.
- [Release notes](https://github.com/egor-tensin/cleanup-path/releases)
- [Commits](https://github.com/egor-tensin/cleanup-path/compare/v4...v5)
---
updated-dependencies:
- dependency-name: egor-tensin/cleanup-path
dependency-version: '5'
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |\
| |
| |
| |
| | |
egor-tensin/dependabot/github_actions/actions/upload-artifact-7
build(deps): bump actions/upload-artifact from 6 to 7
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 6 to 7.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](https://github.com/actions/upload-artifact/compare/v6...v7)
---
updated-dependencies:
- dependency-name: actions/upload-artifact
dependency-version: '7'
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
|
| |
Why do I even need this? on: push covers everything I need
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The proper way to do this is to do `cmake --install --strip`, and not
via a function.
|
| |
|
|
|
| |
This has been done for the boost example anyway, and I'm planning to do
this.
|
| |
|
|
|
|
| |
Since I've been transitioning to Boost's CMake files, the shortcut where
I just specify LIBRARYDIR & USE_STATIC_RUNTIME doesn't seem to work
anymore, so we're fighting.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
It's not supported on GitHub Actions yet.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Boost 1.69.0 was released 7 years ago; I think it's time to let go.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
I was testing the new version (C++20) with some existing code, and
immediately got build errors.
Apparently, now this:
const auto s = u8"hello";
means that s has the type of const char8_t *const, where char8_t is some
batshit insanity with 0 backwards compatibility. For example, you cannot
make a std::string out of this??? Fuck that, and fuck C++ committee
morons.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Accordingly, rename cmake-build to project-build.
|
| |
|
|
|
|
| |
It doesn't make a lot of sense for the build dir argument to be
optional. There's still a placeholder you can use to build in a
temporary directory.
|
| | |
|
| |
|
|
|
| |
I seriously can't believe I didn't have warnings enabled for Clang. That
is so, so dumb.
|
| | |
|