| commit | ab069c6b46d116ac81e8dceb9b3109c445081dbb | [log] [download] |
|---|---|---|
| author | Simon Butcher <simon.butcher@arm.com> | Thu Jun 23 21:42:26 2016 +0100 |
| committer | Simon Butcher <simon.butcher@arm.com> | Thu Jun 23 21:42:26 2016 +0100 |
| tree | 9cb81884d01826de9c42e90a41fdf8bb7b401194 | |
| parent | c8dd1148f0bb8f1dc4e941db932debca83b09e88 [diff] | |
| parent | e7be5bdb968c33322857034c78263065575f5eff [diff] |
Merge branch 'development' into development-restricted
mbed TLS should build out of the box on most systems. Some platform specific options are available in the fully-documented configuration file include/mbedtls/config.h, which is also the place where features can be selected. This file can be edited manually, or in a more programmatic way using the Perl script scripts/config.pl (use --help for usage instructions).
Compiler options can be set using standard variables such as CC and CFLAGS when using the Make and CMake build system (see below).
There are currently four active build systems within the mbed TLS releases:
The main systems used for development are CMake and yotta. Those systems are always complete and up-to-date. The others should reflect all changes present in the CMake and yotta build system, but some features are not ported there by default.
Please note that the yotta option is slightly different from the other build systems:
The Make and CMake build systems create three libraries: libmbedcrypto, libmbedx509, and libmbedtls. Note that libmbedtls depends on libmbedx509 and libmbedcrypto, and libmbedx509 depends on libmbedcrypto. As a result, some linkers will expect flags to be in a specific order, for example the GNU linker wants -lmbedtls -lmbedx509 -lmbedcrypto. Also, when loading shared libraries using dlopen(), you'll need to load libmbedcrypto first, then libmbedx509, before you can load libmbedtls.
yotta is a package manager and build system developed by mbed; it is the build system of mbed OS. To install it on your platform, please follow the yotta installation instructions.
Once yotta is installed, you can use it to download the latest version of mbed TLS form the yotta registry with:
yotta install mbedtls
and build it with:
yotta build
If, on the other hand, you already have a copy of mbed TLS from a source other than the yotta registry, for example from cloning our GitHub repository, or from downloading a tarball of the standalone edition, then you'll need first need to generate the yotta module by running:
yotta/create-module.sh
from the mbed TLS root directory. This will create the yotta module in the yotta/module directory. You can then change to that directory and build as usual:
cd yotta/module yotta build
In any case, you‘ll probably want to set the yotta target before building unless it’s already set globally; for more information on using yotta, please consult the yotta documentation.
For more details on the yotta/mbed OS edition of mbed TLS, including example programs, please consult the Readme at the root of the yotta module.
We intentionally only use the absolute minimum of Make functionality, as a lot of Make features are not supported on all different implementations of Make on different platforms. As such, the Makefiles sometimes require some handwork or export statements in order to work for your platform.
In order to build the source using Make, just enter at the command line:
make
In order to run the tests, enter:
make check
The tests need Perl to be built and run. If you don't have Perl installed, you can skip building the tests with:
make no_test
You'll still be able to run a much smaller set of tests with:
programs/test/selftest
In order to build for a Windows platform, you should use WINDOWS_BUILD=1 if the target is Windows but the build environment is Unix-like (for instance when cross-compiling, or compiling from an MSYS shell), and WINDOWS=1 if the build environment is a Windows shell (for instance using mingw32-make) (in that case some targets will not be available).
Setting the variable SHARED in your environment will build shared libraries in addition to the static libraries. Setting DEBUG gives you a debug build. You can override CFLAGS and LDFLAGS by setting them in your environment or on the make command line; if you do so, essential parts such as -I will still be preserved. Warning options may be overridden separately using WARNING_CFLAGS.
Depending on your platform, you might run into some issues. Please check the Makefiles in library/, programs/ and tests/ for options to manually add or remove for specific platforms. You can also check the mbed TLS Knowledge Base for articles on your platform or issue.
In case you find that you need to do something else as well, please let us know what, so we can add it to the KB.
In order to build the source using CMake, just enter at the command line:
cmake . make
In order to run the tests, enter:
make test
The test suites need Perl to be built. If you don‘t have Perl installed, you’ll want to disable the test suites with:
cmake -DENABLE_TESTING=Off .
If you disabled the test suites, but kept the programs enabled, you can still run a much smaller set of tests with:
programs/test/selftest
To configure CMake for building shared libraries, use:
cmake -DUSE_SHARED_MBEDTLS_LIBRARY=On .
There are many different build modes available within the CMake buildsystem. Most of them are available for gcc and clang, though some are compiler-specific:
Switching build modes in CMake is simple. For debug mode, enter at the command line:
cmake -D CMAKE_BUILD_TYPE=Debug .
To list other available CMake options, use:
cmake -LH
Note that, with CMake, if you want to change the compiler or its options after you already ran CMake, you need to clear its cache first, e.g. (using GNU find):
find . -iname '*cmake*' -not -name CMakeLists.txt -exec rm -rf {} +
CC=gcc CFLAGS='-fstack-protector-strong -Wa,--noexecstack' cmake .
The build files for Microsoft Visual Studio are generated for Visual Studio 2010.
The solution file mbedTLS.sln contains all the basic projects needed to build the library and all the programs. The files in tests are not generated and compiled, as these need a perl environment as well. However, the selftest program in programs/test/ is still available.
We've included example programs for a lot of different features and uses in programs/. Most programs only focus on a single feature or usage scenario, so keep that in mind when copying parts of the code.
mbed TLS includes an elaborate test suite in tests/ that initially requires Perl to generate the tests files (e.g. test\_suite\_mpi.c). These files are generated from a function file (e.g. suites/test\_suite\_mpi.function) and a data file (e.g. suites/test\_suite\_mpi.data). The function file contains the test functions. The data file contains the test cases, specified as parameters that will be passed to the test function.
For machines with a Unix shell and OpenSSL (and optionally GnuTLS) installed, additional test scripts are available:
tests/ssl-opt.sh runs integration tests for various TLS options (renegotiation, resumption, etc.) and tests interoperability of these options with other implementations.tests/compat.sh tests interoperability of every ciphersuite with other implementations.tests/scripts/test-ref-configs.pl test builds in various reduced configurations.tests/scripts/key-exchanges.pl test builds in configurations with a single key exchange enabledtests/scripts/all.sh runs a combination of the above tests, plus some more, with various build options (such as ASan, full config.h, etc).We provide some non-standard configurations focused on specific use cases in the configs/ directory. You can read more about those in configs/README.txt
We gratefully accept bug reports and contributions from the community. There are some requirements we need to fulfill in order to be able to integrate contributions: