> We caught another bug report from CMake. This one is confounding because > the cause of the bug is fixing a previous CMake bug, and the previous fix > was in accordance with CMake recommendations. Also see > https://github.com/weidai11/cryptopp/issues/486. > > CMake is responsible for 18% of the bugs in the bug reporter. Its not easy > to maintain and its a constant source of problems. It picks awful flags by > default and its difficult to change them. Its also poorly documented, so we > often don't know how to fix problems when they arise. > > I'd like to remove CMake from the library and add it to the Patch Page on > the wiki. The patch page is where we place stuff that's helpful for users > but not a good fit for the library. CMake and its problems clearly falls > into the category. Others in the category include the PEM Pack and OS > Protected Storage classes. Also see > https://www.cryptopp.com/wiki/Category:Patch. > > Moving CMake from the library sources to the patch page means > CMakeList.txt will still be available as a download from > https://www.cryptopp.com/wiki/CMake. It also means the community who uses > it will have to maintain it instead of the project. > > Are there any persuasive arguments to keep CMake associated with the > project's sources? >
Last call for patches to CMake before we move it the the patch page. We added an informational sunset message to the existing CMakeList.txt file. Also see https://github.com/weidai11/cryptopp/commit/1c740b0a097aecaa. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
