| /mbedtls-development/tests/scripts/ |
| A D | test_config_script.py | 40 def output_file_name(directory, stem, extension): argument
41 return os.path.join(directory,
45 def cleanup_directory(directory): argument
48 pattern = output_file_name(directory, '*', extension)
53 def prepare_directory(directory): argument
58 if os.path.exists(directory):
59 cleanup_directory(directory)
61 os.makedirs(directory)
|
| A D | check_test_cases.py | 129 for directory in test_directories:
130 for data_file_name in glob.glob(os.path.join(directory, 'suites',
133 ssl_opt_sh = os.path.join(directory, 'ssl-opt.sh')
|
| A D | generate_test_code.py | 1129 for directory in [out_c_file_dir, out_data_file_dir]:
1130 if not os.path.exists(directory):
1131 os.makedirs(directory)
|
| /mbedtls-development/scripts/ |
| A D | windows_msbuild.bat | 13 @rem If the %USERPROFILE%\Source directory exists, then running
14 @rem vcvarsall.bat will silently change the directory to that directory.
16 @rem to that directory instead.
|
| /mbedtls-development/programs/test/cmake_package_install/ |
| A D | CMakeLists.txt | 5 # install into a directory inside our own build directory.
|
| /mbedtls-development/tests/git-scripts/ |
| A D | README.md | 7 The mbed TLS git hooks are located in `<mbed TLS root>/tests/git-scripts` directory, and one must c…
11 Execute the following command to create a link on linux from the mbed TLS `.git/hooks` directory:
|
| /mbedtls-development/docs/proposed/ |
| A D | README | 1 The documents in this directory are proposed specifications for Mbed
|
| /mbedtls-development/tests/ |
| A D | CMakeLists.txt | 5 # Set the project root directory if it's not already defined, as may happen if
25 --directory suites
31 # Derive generated file paths in the build directory
46 --directory ${CMAKE_CURRENT_BINARY_DIR}/suites
|
| A D | Descriptions.txt | 2 The various 'test_suite_XXX' programs from the 'tests' directory, executed
|
| /mbedtls-development/ |
| A D | SUPPORT.md | 7 - the `docs` directory in the source tree;
|
| A D | CMakeLists.txt | 42 # Set the project root directory.
109 # Create a symbolic link from ${base_name} in the binary directory
110 # to the corresponding path in the source directory.
253 # The C files in tests/src directory contain test code shared among test suites
300 … COMMAND lcov --capture --initial --directory library/CMakeFiles/mbedtls.dir -o files.info
301 COMMAND lcov --capture --directory library/CMakeFiles/mbedtls.dir -o tests.info
|
| A D | .gitignore | 38 # Microsoft CMake extension for Visual Studio Code generates a build directory by default
|
| A D | Makefile | 149 lcov --capture --initial --directory library -o files.info
150 lcov --rc lcov_branch_coverage=1 --capture --directory library -o tests.info
|
| A D | .travis.yml | 38 # Add the directory where the Choco packages go
|
| /mbedtls-development/programs/test/cmake_package/ |
| A D | CMakeLists.txt | 5 # skip installing it, and use the build directory directly instead.
|
| /mbedtls-development/programs/test/cmake_subproject/ |
| A D | CMakeLists.txt | 6 # We use the parent Mbed TLS directory as the MBEDTLS_DIR for this test. Other
|
| /mbedtls-development/ChangeLog.d/ |
| A D | 00README.md | 1 # Pending changelog entry directory
3 This directory contains changelog entries that have not yet been merged
|
| /mbedtls-development/configs/ |
| A D | README.txt | 1 This directory contains example configuration files.
|
| /mbedtls-development/3rdparty/everest/ |
| A D | README.md | 1 The files in this directory stem from [Project Everest](https://project-everest.github.io/) and are…
|
| /mbedtls-development/programs/ssl/ |
| A D | CMakeLists.txt | 26 # inside the same directory, so we need to propagate manually.
|
| /mbedtls-development/programs/test/ |
| A D | generate_cpp_dummy_build.sh | 10 Run this program from the root of an Mbed TLS directory tree or from
|
| A D | CMakeLists.txt | 47 # this file will also be used in another directory, so create a target, see
|
| /mbedtls-development/doxygen/ |
| A D | mbedtls.doxyfile | 48 # Doxygen will copy the logo to the output directory.
63 # source files, where putting all generated files in the same directory would
140 # If left blank the directory from which doxygen is run is used as the
928 # the output directory.
993 # HTML output directory. Running make will produce the docset in that
994 # directory and running "make install" will install the docset in
1036 # written to the html output directory.
1128 # the directory within the plugins directory should be the same as
1213 # directory is located at the same level as the HTML output directory, then
1311 # Makefile that is written to the output directory.
[all …]
|
| /mbedtls-development/tests/data_files/dir4/ |
| A D | Readme | 1 This directory contains the certificates for the tests targeting the enforcement of the policy indi…
|
| /mbedtls-development/programs/fuzz/ |
| A D | README.md | 4 This directory contains fuzz targets.
|