> > With the latest release I have experienced several times that the flags > used during cryptopp compilation (especially automatically set in the > makefile) are not the same for my software, resulting in link failures. (I > had to manually add -DCRYPTOPP_DISABLE_ASM to resolve my particular issue.) >
I know exactly what you are talking about. CRYPTOPP_DISABLE_ASM is a prime example of the problem. Its set in the makefile, but its not recorded in config.h. I even talked about it here: https://github.com/weidai11/cryptopp/issues/11. From Issue 11: Maybe we will be able to test in the makefile, and then define/undefine CRYPTOPP_USING_CLANG_INTEGRATED_ASSEMBLER using sed. This way, config.h stays in sync with the actual build tools and settings. > Would it be better to create a config (something like cryptopp-config.hpp) > file (different from the current config.h) which records all defines > inferred during "configuration" stage in the makefile? > That's something else to think about. 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.
