2f1ae5a86e
Also change the include path of crypto_spe.h in crypto_platform.h to allow the former file to be included in library-only builds. Signed-off-by: Aditya Deshpande <aditya.deshpande@arm.com> |
||
---|---|---|
.. | ||
config-ccm-psk-dtls1_2.h | ||
config-ccm-psk-tls1_2.h | ||
config-no-entropy.h | ||
config-suite-b.h | ||
config-symmetric-only.h | ||
config-thread.h | ||
crypto_config_profile_medium.h | ||
README.txt | ||
tfm_mbedcrypto_config_profile_medium.h |
This directory contains example configuration files. The examples are generally focused on a particular usage case (eg, support for a restricted number of ciphersuites) and aim at minimizing resource usage for this target. They can be used as a basis for custom configurations. These files are complete replacements for the default mbedtls_config.h. To use one of them, you can pick one of the following methods: 1. Replace the default file include/mbedtls/mbedtls_config.h with the chosen one. 2. Define MBEDTLS_CONFIG_FILE and adjust the include path accordingly. For example, using make: CFLAGS="-I$PWD/configs -DMBEDTLS_CONFIG_FILE='<foo.h>'" make Or, using cmake: find . -iname '*cmake*' -not -name CMakeLists.txt -exec rm -rf {} + CFLAGS="-I$PWD/configs -DMBEDTLS_CONFIG_FILE='<foo.h>'" cmake . make Note that the second method also works if you want to keep your custom configuration file outside the mbed TLS tree.