mbedtls/configs
Bence Szépkúti ba7248abc4 Introduce versioning in the config files
Signed-off-by: Bence Szépkúti <bence.szepkuti@arm.com>
2021-06-28 09:28:47 +01:00
..
config-ccm-psk-tls1_2.h Introduce versioning in the config files 2021-06-28 09:28:47 +01:00
config-no-entropy.h Introduce versioning in the config files 2021-06-28 09:28:47 +01:00
config-suite-b.h Introduce versioning in the config files 2021-06-28 09:28:47 +01:00
config-symmetric-only.h Introduce versioning in the config files 2021-06-28 09:28:47 +01:00
config-thread.h Introduce versioning in the config files 2021-06-28 09:28:47 +01:00
README.txt Rename config.h to mbedtls_config.h 2021-06-28 09:28:33 +01:00

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.
   (Depending on your compiler, you may need to adjust the line with
   #include "mbedtls/check_config.h" then.)

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.