diff options
| author | Egor Tensin <Egor.Tensin@gmail.com> | 2023-07-03 22:31:15 +0200 |
|---|---|---|
| committer | Egor Tensin <Egor.Tensin@gmail.com> | 2023-07-03 22:32:44 +0200 |
| commit | be0b69971a4d8447d86f77b3d09b3820e8c9cb67 (patch) | |
| tree | da1e2075e9145186f92e28fea6061802d0842fca /README.md | |
| parent | project.ci.cmake -> project.ci.build (diff) | |
| download | cmake-common-be0b69971a4d8447d86f77b3d09b3820e8c9cb67.tar.gz cmake-common-be0b69971a4d8447d86f77b3d09b3820e8c9cb67.zip | |
remove project.ci
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.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 23 |
1 files changed, 0 insertions, 23 deletions
@@ -26,8 +26,6 @@ Installation | boost-download | `python3 -m project.boost.download` | boost-build | `python3 -m project.boost.build` | project-build | `python3 -m project.build` - | ci-boost | `python3 -m project.ci.boost` - | ci-build | `python3 -m project.ci.build` Toolsets -------- @@ -102,27 +100,6 @@ Windows-specific macros, strips debug symbols in release builds, etc.). Everything is optional (use the `CC_*` CMake options to opt out). -### CI - -Utility scripts `ci-boost` and `ci-build` allow building Boost and CMake -projects on multiple CI systems. -They work by calling the generic scripts from above, auto-filling some -parameters from environment variables. - -| | Travis | AppVeyor | GitHub Actions -| ----------------- | ------------------------------------ | ------------------------------------------ | -------------- -| `--toolset` | `$TOOLSET` | `%TOOLSET%` | `$TOOLSET` -| `--platform` | `$PLATFORM` | `%PLATFORM%` | `$PLATFORM` -| `--configuration` | `$CONFIGURATION` | `%CONFIGURATION%` | `$CONFIGURATION` -| Boost version | `$BOOST_VERSION` | `%BOOST_VERSION%` | `$BOOST_VERSION` -| Boost path | `$TRAVIS_BUILD_DIR/../build/boost` | `%APPVEYOR_BUILD_FOLDER%\..\build\boost` | `$GITHUB_WORKSPACE/../build/boost` -| Build path | `$TRAVIS_BUILD_DIR/../build/cmake` | `%APPVEYOR_BUILD_FOLDER%\..\build\cmake` | `$GITHUB_WORKSPACE/../build/cmake` -| Install path | `$TRAVIS_BUILD_DIR/../build/install` | `%APPVEYOR_BUILD_FOLDER%\..\build\install` | `$GITHUB_WORKSPACE/../build/install` - - -For an example of how to integrate `ci-boost` and `ci-build` into a CI -workflow, see [docs/ci.md](docs/ci.md). - Tools ----- |