Searched full:build (Results 1 – 25 of 172) sorted by relevance
1234567
| /mbedtls-3.4.0/visualc/VS2010/ |
| D | mbedTLS.sln | 290 {46CF2D25-6A36-4189-B59C-E4815388E554}.Debug|Win32.Build.0 = Debug|Win32
292 {46CF2D25-6A36-4189-B59C-E4815388E554}.Debug|x64.Build.0 = Debug|x64
294 {46CF2D25-6A36-4189-B59C-E4815388E554}.Release|Win32.Build.0 = Release|Win32
296 {46CF2D25-6A36-4189-B59C-E4815388E554}.Release|x64.Build.0 = Release|x64
298 {5DBB9FC3-6FD6-CA8D-E0FA-35F1E75EFAE7}.Debug|Win32.Build.0 = Debug|Win32
300 {5DBB9FC3-6FD6-CA8D-E0FA-35F1E75EFAE7}.Debug|x64.Build.0 = Debug|x64
302 {5DBB9FC3-6FD6-CA8D-E0FA-35F1E75EFAE7}.Release|Win32.Build.0 = Release|Win32
304 {5DBB9FC3-6FD6-CA8D-E0FA-35F1E75EFAE7}.Release|x64.Build.0 = Release|x64
306 {1E959679-AB4C-F434-E078-BAA4DC2159E9}.Debug|Win32.Build.0 = Debug|Win32
308 {1E959679-AB4C-F434-E078-BAA4DC2159E9}.Debug|x64.Build.0 = Debug|x64
[all …]
|
| /mbedtls-3.4.0/tests/scripts/ |
| D | all.sh | 34 # Warning: the test is destructive. It includes various build modes and
84 # * component_build_XXX: build things but don't run them.
85 # * component_test_XXX: build and test.
154 # See also RELEASE_SEED in basic-build-test.sh. Debugging is easier if
157 # basic-build-test.sh as well.
253 --restore First clean up the build tree, restoring backed up
266 --out-of-source-dir=<path> Directory used for CMake out-of-source build tests.
304 rm -rf programs/test/cmake_subproject/build
309 rm -rf programs/test/cmake_package/build
314 rm -rf programs/test/cmake_package_install/build
[all …]
|
| D | docker_env.sh | 68 # Build the Docker image
70 ${DOCKER} image build \
73 --build-arg MAKEFLAGS_PARALLEL="-j ${NUM_PROC}" \
75 ${http_proxy+--build-arg http_proxy=${http_proxy}} \
76 ${https_proxy+--build-arg https_proxy=${https_proxy}} \
77 ${MBEDTLS_DOCKER_REGISTRY+--build-arg MY_REGISTRY="${MBEDTLS_DOCKER_REGISTRY}/"} \
|
| D | psa_collect_statuses.py | 4 1. Build Mbed Crypto with -DRECORD_PSA_STATUS_COVERAGE_LOG
11 The build command is "make -DRECORD_PSA_STATUS_COVERAGE_LOG", which is
12 only supported with make (as opposed to CMake or other build methods).
83 """Build and run unit tests and report observed function return statuses.
85 Build Mbed Crypto with -DRECORD_PSA_STATUS_COVERAGE_LOG, run the
|
| D | depends.py | 33 - commands to be run on each job (only build, build and test, or any other custom);
38 - ComplementaryDomain - build a job for each passed symbol by disabling a single
41 - ExclusiveDomain - build a job where, for each passed symbol, only this particular
165 """Build a job object.
203 '''Run the job's build and test commands.
207 other commands are run (typically, the first command is a build command
208 and subsequent commands are tests that cannot run if the build failed).'''
331 """Build a domain for the specified list of configuration symbols.
359 """Build a domain for the specified list of configuration symbols.
432 # Key exchange types. Only build the library and the sample
|
| D | basic-build-test.sh | 3 # basic-build-test.sh
39 # Usage: basic-build-test.sh
79 # Step 0 - print build environment info
89 # Step 1 - Make and instrumented build for code coverage
162 rm -f "tests/basic-build-test-$$.ok"
277 touch "basic-build-test-$$.ok"
289 rm "tests/basic-build-test-$$.ok"
|
| /mbedtls-3.4.0/tests/docker/bionic/ |
| D | Dockerfile | 5 # Defines a Docker container suitable to build and run all tests (all.sh),
38 # mbedtls build/test dependencies
39 build-essential \
57 # libnettle build dependencies
67 # Build a static, legacy openssl from sources with sslv3 enabled
68 # Based on https://gist.github.com/bmaupin/8caca3a1e8c3c5686141 (build-openssl.sh)
69 # Note: openssl-1.0.2 and earlier has known build issues with parallel make.
79 # Build OPENSSL as 1.0.2g
89 # Build a new openssl binary for ARIA/CHACHA20 support
90 # Based on https://gist.github.com/bmaupin/8caca3a1e8c3c5686141 (build-openssl.sh)
[all …]
|
| /mbedtls-3.4.0/ |
| D | README.md | 11 Mbed TLS should build out of the box on most systems. Some platform specific options are available …
13 …ronment variables such as `CC` and `CFLAGS` when using the Make and CMake build system (see below).
35 There are currently three active build systems used within Mbed TLS releases:
41 …date. The others should reflect all changes present in the CMake and Make build system, although f…
43 The Make and CMake build systems create three libraries: libmbedcrypto, libmbedx509, and libmbedtls…
47 You need the following tools to build the library with the provided makefiles:
49 * GNU Make 3.82 or a build tool that CMake supports.
63 * Perl, for some library source files and for Visual Studio build files.
82 …uire GNU Make. To build the library and the sample programs, GNU Make and a C compiler are suffici…
86 In order to build from the source code using GNU Make, just enter at the command line:
[all …]
|
| D | .gitignore | 4 # CMake build artifacts:
17 # Test coverage build artifacts:
31 # MSVC build artifacts:
37 # Python build artifacts:
43 # Microsoft CMake extension for Visual Studio Code generates a build directory by default
44 /build/
|
| D | .travis.yml | 36 # Do a manual build+test sequence rather than using all.sh,
38 # which is a build with Clang >= 10 and ASan, running all the SSL
66 # Windows Build Environment. And 'generic' causes the job to get stuck
|
| D | CMakeLists.txt | 2 # CMake build system design considerations:
55 option(ENABLE_PROGRAMS "Build mbed TLS programs." ON)
74 option(ENABLE_TESTING "Build mbed TLS tests." OFF)
76 option(ENABLE_TESTING "Build mbed TLS tests." ON)
117 …CACHE STRING "Choose the type of build: None Debug Release Coverage ASan ASanDbg MemSan MemSanDbg …
336 # Make scripts needed for testing available in an out-of-source build.
|
| /mbedtls-3.4.0/docs/proposed/ |
| D | psa-driver-integration-guide.md | 6 This document describes how to build Mbed TLS with additional cryptoprocessor drivers that follow t…
12 The PSA cryptography driver interface provides a way to build Mbed TLS with additional code that im…
16 …driver description files** in JSON format and some code to include in the build. The driver code c…
18 ## How to build Mbed TLS with drivers
20 To build Mbed TLS with drivers:
|
| D | psa-conditional-inclusion-c.md | 4 This document is a proposed interface for deciding at build time which cryptographic mechanisms to …
18 Mbed TLS offers a way to select which cryptographic mechanisms are included in a build through its …
30 … application does not require a mechanism, a suitably configured Mbed TLS build must not include i…
32 [Req.drivers] If a PSA driver is available in the build, a suitably configured Mbed TLS build must …
34 [Req.c] The configuration mechanism consists of C preprocessor definitions, and the build does not …
79 …ion in the PSA Crypto configuration file, it may still be included in the build, either because th…
134 … in `mbedtls/config_psa.h` are needed not only to build the PSA parts of the library, but also to …
186 …chanism for a PSA service is in JSON syntax. The translation from JSON to build instructions is no…
|
| /mbedtls-3.4.0/scripts/data_files/ |
| D | vs2010-sln-template.sln | 16 {46CF2D25-6A36-4189-B59C-E4815388E554}.Debug|Win32.Build.0 = Debug|Win32
18 {46CF2D25-6A36-4189-B59C-E4815388E554}.Debug|x64.Build.0 = Debug|x64
20 {46CF2D25-6A36-4189-B59C-E4815388E554}.Release|Win32.Build.0 = Release|Win32
22 {46CF2D25-6A36-4189-B59C-E4815388E554}.Release|x64.Build.0 = Release|x64
|
| /mbedtls-3.4.0/scripts/ |
| D | windows_msbuild.bat | 1 @rem Build and test Mbed TLS with Visual Studio using msbuild.
4 @rem https://docs.microsoft.com/en-us/cpp/build/how-to-modify-the-target-framework-and-…
9 set "vcvarsall=C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vc…
|
| /mbedtls-3.4.0/docs/architecture/psa-migration/ |
| D | testing.md | 11 There needs to be at least one build in `all.sh` that enables
14 `MBEDTLS_USE_PSA_CRYPTO`. There needs to be at least one build with
80 covered by running the existing TLS tests in a build with
94 be already be covered by running the existing tests in a build with
|
| D | strategy.md | 48 Also, we can't just auto-enable `MBEDTLS_ENTROPY_C` as it doesn't build
89 auto-enable the latter, as it won't build or work out of the box on all
102 the standard function, for driver support in build with entropy.)
230 a. the library to build in a reasonably-complete configuration,
298 break of backwards compatibility, as it was previously impossible to build in
299 those configurations, and in configurations were the build was possible,
345 only be included in the build if it is possible to use that hash in some way.
379 that build and run tests in newly-supported configurations. For example, if
391 - the set of tests skipped in the driver-only build is the same as in an
396 driver-only build. In other cases, analysis of the outcome files is needed,
|
| /mbedtls-3.4.0/programs/fuzz/ |
| D | README.md | 30 mkdir build
31 cd build
50 * Build mbedtls programs ssl_server2 and ssl_client2
|
| /mbedtls-3.4.0/programs/test/cmake_package/ |
| D | CMakeLists.txt | 5 # skip installing it, and use the build directory directly instead.
20 --build "${MbedTLS_BINARY_DIR}")
|
| D | cmake_package.c | 26 /* The main reason to build this is for testing the CMake build, so the program
|
| /mbedtls-3.4.0/programs/test/cmake_package_install/ |
| D | CMakeLists.txt | 5 # install into a directory inside our own build directory.
22 --build "${MbedTLS_BINARY_DIR}"
|
| D | cmake_package_install.c | 27 /* The main reason to build this is for testing the CMake build, so the program
|
| /mbedtls-3.4.0/library/ |
| D | common.h | 130 * byte of the four bytes to build the 32 bits unsigned
168 * byte of the four bytes to build the 32 bits unsigned
206 * byte of the two bytes to build the 16 bits unsigned
240 * byte of the two bytes to build the 16 bits unsigned
274 * byte of the three bytes to build the 24 bits unsigned
310 * byte of the three bytes to build the 24 bits unsigned
346 * byte of the eight bytes to build the 64 bits unsigned
392 * byte of the eight bytes to build the 64 bits unsigned
|
| D | CMakeLists.txt | 1 option(USE_STATIC_MBEDTLS_LIBRARY "Build mbed TLS static library." ON)
2 option(USE_SHARED_MBEDTLS_LIBRARY "Build mbed TLS shared library." OFF)
199 option(MSVC_STATIC_RUNTIME "Build the libraries with /MT compiler flag" OFF)
234 message(FATAL_ERROR "Need to choose static or shared mbedtls build!")
|
| /mbedtls-3.4.0/programs/test/cmake_subproject/ |
| D | cmake_subproject.c | 27 /* The main reason to build this is for testing the CMake build, so the program
|
1234567
