Jakub Zakrzewski
Jakub Zakrzewski
I'd argue that short names are not good for scripts. I tend to do the opposite - if I use an option frequently, I'll abbreviate it (if I can remember...
On platforms supporting RPATH/RUNPATH CMake uses them by default AFAIR, so the binaries in the build tree can find everything. This is again removed during the install phase. And for...
Especially because it's basically a build script, so even if we generously assume GPL had to be expanded on other files (seems really silly), it'd only expand on other autotools...
I suspect this is the same problem I patch locally when building curl - I haven't upstreamed that because I had no time to check if it has any unwanted...
From the link you've posted: > If the running version of CMake is older than 3.12, the extra ... dots will be seen as version component separators, resulting in the...
It's not CMake that throws errors but VS 2017 itself trying to analyse the version string. See: [CMake issue](https://gitlab.kitware.com/cmake/cmake/-/issues/18178) and [VS Issue](https://developercommunity.visualstudio.com/t/cmake-312-version-requirements-definition-fails-fo/294070) for reference.
A wild idea - fail if no local node can be detected but point users to "dweb.link" that they can enable if they trust them. It could still be seen...
@henryiii they are not "dereferencing twice" - they just iterate the old style - with an iterator that itself needs to be dereferenced. I think you're referring to a fact,...
The "introduced in ..." is better IMHO. It's easier to get an overview of what's available in which version and avoids confusion (like reading new docs when you have older...
Single header-only mode is useful for quick prototyping but I'd really like an option to have a "regular" library - the one where the implementation can be compiled into a...