Closed lzy1g1225 closed 2 years ago
cryptopp-cmake tracks crypto++ version manually for a good reason: every release of crypto++ may add source files, change compiler options, add compiler definitions, etc... we don't want to encourage an automatic download of the latest version of crypto++ and a cmake release that does not do the due diligence.
Therefore, the process is: we explicitly know which version we are currently tracking, we set it, we do the due diligence, update the cmake files.
Now crypto++ gets auto-fetched, so there is zero overhead for the user to do anything. Once we release a tag for cryptopp-cmake with certain version number of crypto++, everything is automatic.
Find out the source code version from header file config_ver.h, so we don't need to set it mannually