Hi! I would like to propose a small discussion about cryptopp build process. Right now, all of the system detection is done either in the makefile or directly with pre-processor directives in the source files. This works perfectly fine for cryptopp compilation itself, but not always so great for projects using cryptopp.
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.) 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? --- Alex -- -- 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
