Update year references from 2021 to 2022
This commit is contained in:
parent
e524411ec7
commit
6020c1c22b
@ -4,7 +4,7 @@ People love to hate build systems.
|
||||
Just watch the talks from CppCon17 to see examples of developers making the state of build systems the brunt of jokes.
|
||||
This raises the question: Why?
|
||||
Certainly there are no shortage of problems when building.
|
||||
But I think that, in 2021, we have a very good solution to quite a few of those problems.
|
||||
But I think that, in 2022, we have a very good solution to quite a few of those problems.
|
||||
It's CMake. Not CMake 2.8 though; that was released before C++11 even existed!
|
||||
Nor the horrible examples out there for CMake (even those posted on KitWare's own tutorials list).
|
||||
I'm talking about Modern CMake. CMake 3.4+, maybe even CMake 3.22+!
|
||||
|
@ -23,7 +23,7 @@ The next two lists are heavily based on the excellent gist [Effective Modern CMa
|
||||
* **Use `cmake_policy` and/or range of versions**: Policies change for a reason. Only piecemeal set OLD policies if you have to.
|
||||
|
||||
|
||||
## Selecting a minimum in 2021:
|
||||
## Selecting a minimum in 2022:
|
||||
|
||||
What minimum CMake should you _run_ locally, and what minimum should you _support_ for people using your
|
||||
code? Since you are reading this, you should be able to get a release in the last few versions of CMake;
|
||||
|
Loading…
x
Reference in New Issue
Block a user