aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/examples/dynamic (unfollow)
Commit message (Collapse)Author
2023-07-04common.cmake: downgrade C++ standard versionv4.0Egor Tensin
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.
2023-07-04common.cmake: bump default C++ standardEgor 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.
2020-10-28common.cmake: add install_pdbs()before_toolchain_refactoringEgor Tensin
2020-03-28WIP: restructureEgor Tensin
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.