| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This repo literally started with common.cmake. However, I think that in
this day and age, it is, to put it mildly, outdated. Feature by feature:
* The C++ standard is better defined on a per-project basis, and it's
very easy. Frankly, I'm surprised GCC still (as of March '26) defaults
to something pre-11 (or at least I think it does).
* The warning options are, again, very easy to do on a per-project
basis, and perhaps they should be defined there.
* The Windows-only defines (NOMINMAX, etc.) are, again, very easy to
define on the project level, and don't warrant a separate file.
* The static runtime thing is more tricky. I use static runtime linking
on Windows only, basically. And since about 3.15, it supports
CMAKE_MSVC_RUNTIME_LIBRARY, which can set up the linking without my
help. I don't care about the older versions enough to keep maintenance.
* Symbol stripping is better done when calling `cmake --install --strip`
in modern CMake version. Otherwise, it's a simple compilation flag for
Release builds.
* Installing PDBs does require some trickery though. It's simple enough:
you just call install() with $<TARGET_PDB_FILE> or whatever it's
called.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
I seriously can't believe I didn't have warnings enabled for Clang. That
is so, so dumb.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
Generator expressions aren't evaluated at configuration time. Symbols
were always stripped, unfortunately.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* Add more logging messages.
* Rename user-facing switches.
* Refactor things a bit (a lot).
* Lower the default C++ standard version back to 14 to support CMake 3.1
(meh, there're probably other features in use that are not supported by it).
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
