Closed friedrichsenm closed 2 years ago
I'm certain there are a lot more ways to trigger this!
It's not our target to handle each and every configuration possibility, but only to give a sane set of defaults and enable hard dependencies if you enable a feature.
Please simply remove clashing defines from your configuration.
Prerequisites
Description
Trying to build a minimal version of the library using
LTC_NOTHING
and adding in the respective pieces can result in lots of unnecessary compiler warnings like the following:These come from bits in
tomcrypt_custom.h
like:A simple solution would be to just add an extra check to make sure the macros aren't already defined.
Steps to Reproduce
Compile the library with this set of defines (I'm sure there are more ways of triggering this): DLTC_NOTHING DLTC_RIJNDAEL DLTC_CBC_MODE DLTC_SHA3 DLTC_SHA256 DLTC_SHA384 DLTC_SHA512 DLTC_HASH_HELPERS DLTC_FORTUNA DLTC_MRSA DLTC_NO_RSA_CRT_HARDENING DLTC_NO_RSA_BLINDING DLTC_PKCS_1 DLTC_PKCS_5 DLTC_PKCS_8 DLTC_PKCS_12 DLTC_DER DLTC_HMAC
Version
1.18.2-develop