mbedtls/configs
Ron Eldor 376f7f5fe1 Fix typo in configs/README.txt file
Fix typo in Readme file: ajust->adjust
2017-09-30 21:37:59 +01:00
..
config-ccm-psk-tls1_2.h Make config check include for configs examples more consistent 2015-09-15 21:38:12 +02:00
config-mini-tls1_1.h
config-no-entropy.h Enable MBEDTLS_AES_ROM_TABLES in config-no-entropy 2017-07-27 21:44:32 +01:00
config-picocoin.h Make config check include for configs examples more consistent 2015-09-15 21:38:12 +02:00
config-suite-b.h
config-thread.h Fix build failure for thread config 2016-10-05 14:19:17 +01:00
README.txt Fix typo in configs/README.txt file 2017-09-30 21:37:59 +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 config.h. To use one of
them, you can pick one of the following methods:

1. Replace the default file include/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.