aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/project (follow)
Commit message (Collapse)AuthorAge
...
* project.ci: --install picks the directory automaticallyEgor Tensin2021-01-18
|
* project.cmake: create the build dir if necessaryEgor Tensin2021-01-18
|
* README: updateEgor Tensin2021-01-17
|
* README: updateEgor Tensin2021-01-17
|
* fix PyLint warningsEgor Tensin2021-01-17
|
* 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.
* README: elaborateEgor Tensin2020-10-18
|
* fix build dir path on Travis/AppVeyorEgor Tensin2020-10-04
| | | | | I.e. it used to be just C:\projects instead of C:\projects\build on AppVeyor.
* project.boost.download: add dest_dir parameterEgor Tensin2020-04-04
|
* project.boost.download: --unpack = --cache if specifiedEgor Tensin2020-04-04
|
* project.boost: retry downloadsEgor Tensin2020-03-31
|
* project.cmake: support --mingw for Travis/AppVeyorEgor Tensin2020-03-30
|
* project.ci: dedupe codeEgor Tensin2020-03-30
|
* project.cmake: make it --boost awareEgor Tensin2020-03-30
|
* project.boost.build: switch to --layout=systemEgor Tensin2020-03-30
|
* project.cmake: make it --platform awareEgor Tensin2020-03-30
|
* project.cmake.build: refactoringEgor Tensin2020-03-30
|
* project: code styleEgor Tensin2020-03-30
|
* project.boost: support --mingw for Travis/AppVeyorEgor Tensin2020-03-30
|
* project.build.build: more restrictive defaultsEgor Tensin2020-03-30
|
* project: minor-ish refactoringEgor Tensin2020-03-30
|
* project.boost: first-class MinGW-w64 supportEgor Tensin2020-03-29
|
* project: add os.pyEgor Tensin2020-03-29
|
* fix READMEs, code style, etc.Egor Tensin2020-03-29
|
* project.boost: -d0 by defaultEgor Tensin2020-03-29
|
* project.cmake: insignificant refactoringEgor Tensin2020-03-29
|
* project.cmake: factor out common utilsEgor Tensin2020-03-29
|
* project.boost: factor out everything elseEgor Tensin2020-03-28
| | | | I finally snapped. This starts to resemble sensible structure though.
* project.boost: factor out BoostVersionEgor Tensin2020-03-28
|
* project.boost: factor out Configuration/Platform/LinkageEgor Tensin2020-03-28
|
* WIP: restructureEgor Tensin2020-03-28
A stupid attempt to reduce code duplication led me to believe that all the scripts could use _a bit_ of refactoring. This is going to be a major pain (factoring out all the things), which I'll take gladly. All the links and usage examples are broken right now, but nobody cares, so whatevs.