| /optee_os/lib/libmbedtls/mbedtls/ |
| H A 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.
51 * Python 3.8 to generate the test code. Python is also needed to integrate PSA drivers and to build…
67 * Perl, for some library source files and for Visual Studio build files.
87 …uire GNU Make. To build the library and the sample programs, GNU Make and a C compiler are suffici…
[all …]
|
| H A D | ChangeLog | 82 * Resolved build issue with C++ projects using Mbed TLS 3.6 when compiling
131 largest PSA key enabled in the build.
212 in C++. This resolves a build failure under C++ compilers that do not
217 * In a PSA-client-only build (i.e. MBEDTLS_PSA_CRYPTO_CLIENT &&
306 * Fix TLS 1.3 client build and runtime when support for session tickets is
321 entropy_poll.c and sha_256.c. There was a build warning during
325 * Fix the build when MBEDTLS_PSA_CRYPTO_CONFIG is enabled and the built-in
339 * Fix server mode only build when MBEDTLS_SSL_SRV_C is enabled but
442 * If a cipher or AEAD mechanism has a PSA driver, you can now build the
507 MBEDTLS_PSA_CRYPTO_CLIENT is enabled at build time and psa_crypto_init() is
[all …]
|
| /optee_os/ |
| H A D | CHANGELOG.md | 7 …- OP-TEE/build: [release page][OP_TEE_build_release_4_8_0], [commits][OP_TEE_build_commits_4_8_0] …
23 [OP_TEE_build_release_4_8_0]: https://github.com/OP-TEE/build/releases/tag/4.8.0
24 [OP_TEE_build_commits_4_8_0]: https://github.com/OP-TEE/build/compare/4.7.0...4.8.0
25 [OP_TEE_build_pr_4_8_0]: https://github.com/OP-TEE/build/pulls?q=is%3Apr+is%3Amerged+base%3Amaster+…
37 …- OP-TEE/build: [release page][OP_TEE_build_release_4_7_0], [commits][OP_TEE_build_commits_4_7_0] …
53 [OP_TEE_build_release_4_7_0]: https://github.com/OP-TEE/build/releases/tag/4.7.0
54 [OP_TEE_build_commits_4_7_0]: https://github.com/OP-TEE/build/compare/4.6.0...4.7.0
55 [OP_TEE_build_pr_4_7_0]: https://github.com/OP-TEE/build/pulls?q=is%3Apr+is%3Amerged+base%3Amaster+…
67 …- OP-TEE/build: [release page][OP_TEE_build_release_4_6_0], [commits][OP_TEE_build_commits_4_6_0] …
83 [OP_TEE_build_release_4_6_0]: https://github.com/OP-TEE/build/releases/tag/4.6.0
[all …]
|
| H A D | Makefile | 87 define build-ta-target
91 $(foreach t, $(ta-targets), $(eval $(call build-ta-target, $(t))))
93 # Build user TAs included in this git
95 define build-user-ta
97 include ta/mk/build-user-ta.mk
99 $(foreach t, $(sort $(wildcard ta/*/user_ta.mk)), $(eval $(call build-user-ta,$(t))))
|
| /optee_os/core/drivers/crypto/caam/include/ |
| H A D | caam_utils_dmaobj.h | 38 * Initialize and build the SGT/Buffer Object of a CAAM DMA object of type
65 * Initialize and build the SGT/Buffer Object of a CAAM DMA object of type
144 * Build the CAAM DMA Object's sgtbuf input and output with the same data
146 * First try to build input sgtbuf of maximum @length starting at @offset.
147 * Then build output sgtbuf with same input data length built start at @offset.
181 * Build the CAAM DMA Object's sgtbuf object. Try to build a sgtbuf of
|
| H A D | caam_types.h | 25 * user source data to build a full algorithm block buffer
|
| /optee_os/lib/libutils/ext/ |
| H A D | sub.mk | 16 build-ubsan := y
19 build-ubsan := $(CFG_TA_SANITIZE_UNDEFINED)
21 srcs-$(build-ubsan) += ubsan.c
|
| /optee_os/mk/ |
| H A D | cleandirs.mk | 1 # Cleaning directories generated during a previous build,
2 # a failed previous build or even no previous build.
3 # Track build directories through 'cleanfiles'.
|
| H A D | aosp_optee.mk | 16 ## this file to build TAs ##
25 PREBUILT_MAKE ?= prebuilts/build-tools/linux-x86/bin/make
26 # we need this check because the Pie build does not have
32 # The AOSP build tool is not the regular make,
34 # the flag or we would lose parallel build
36 # https://android.googlesource.com/platform/build/kati/+/master/main.cc#100
|
| H A D | config.mk | 16 # Actual values used during the build are output to $(out-dir)/conf.mk
44 # Path to the Python interpreter used by the build system.
46 # path. But build environments that require more explicit control can
98 # - To debug user-mode (TA) allocations: build OP-TEE *and* the TA with:
100 # - To debug TEE core allocations: build OP-TEE with:
124 # Should OPTEE_SMC_CALL_GET_OS_REVISION return a build identifier to Normal
253 # Include lib/libutils/isoc in the build? Most platforms need this, but some
257 # Include lib/libutils/compiler-rt in the build. Most platforms need this.
295 # Build user TAs included in this source tree
390 # Warning: If enabled for release build then it will break rollback protection
[all …]
|
| /optee_os/lib/libutils/isoc/arch/arm/softfloat/doc/ |
| H A D | SoftFloat-source.html | 35 <TR><TD></TD><TD>5.3. Macros for Build Options</TD></TR>
218 build
250 The <CODE>build</CODE> directory is intended to contain a subdirectory for each
251 target platform for which a build of the SoftFloat library may be created.
252 For each build target, the target’s subdirectory is where all derived
255 The two <CODE>template</CODE> subdirectories are not actual build targets but
282 A build of SoftFloat for the specific target is begun by executing the
284 A completely different build tool can be used if an appropriate
290 additional C declarations specific to the build target.
380 As provided, the build process for a target expects to involve exactly
[all …]
|
| /optee_os/.github/workflows/ |
| H A D | ci.yml | 60 name: Build (${{ matrix.name }})
349 - name: Restore build cache
356 - name: Build
378 name: Build QEMUv7 image
391 - name: Build Docker image
393 docker build -t qemuv7_image .
438 - name: Restore build cache
465 cd $TOP/build
472 name: Build QEMUv8 image
485 - name: Build Docker image
[all …]
|
| /optee_os/scripts/ |
| H A D | gen_compile_commands.py | 8 # Briefly documented at doc/build/gen_compile_commands.rst
28 # The tools/ directory adopts a different build system, and produces .cmd
46 directory_help = ('specify the output directory used for the OP-TEE build '
106 """Return the path of .cmd file used for the given build artifact
121 Parse the given archive, and yield every .cmd file used to build it.
136 Parse the given modules.order, and yield every .cmd file used to build the
|
| /optee_os/core/lib/scmi-server/ |
| H A D | sub.mk | 7 # The toolchain build directive must also match the list of
44 produce-fwk_module_list = build/framework/src/fwk_module_list.c
45 recipe-fwk_module_list = cmake -S $(scpfw-path) -B $(scpfw-out-path)/build \
49 incdirs_ext-y += $(scpfw-out-path)/build/framework/include
|
| /optee_os/lib/libmbedtls/mbedtls/library/ |
| H A D | alignment.h | 33 * https://learn.microsoft.com/en-us/cpp/build/arm64-windows-abi-conventions?view=msvc-170#alignment
409 * byte of the four bytes to build the 32 bits unsigned
445 * byte of the four bytes to build the 32 bits unsigned
482 * byte of the two bytes to build the 16 bits unsigned
518 * byte of the two bytes to build the 16 bits unsigned
554 * byte of the three bytes to build the 24 bits unsigned
586 * byte of the three bytes to build the 24 bits unsigned
618 * byte of the eight bytes to build the 64 bits unsigned
654 * byte of the eight bytes to build the 64 bits unsigned
|
| H A D | psa_crypto_invasive.h | 20 * Include the build-time configuration information header. Here, we do not
23 * TF-PSA-Crypto repository which has a different build system and
|
| H A D | psa_crypto_se.h | 13 * Include the build-time configuration information header. Here, we do not
16 * TF-PSA-Crypto repository which has a different build system and
|
| /optee_os/lib/libmbedtls/mbedtls/include/psa/ |
| H A D | crypto_platform.h | 26 * Include the build-time configuration information header. Here, we do not
29 * TF-PSA-Crypto repository which has a different build system and
|
| H A D | build_info.h | 4 * \brief Build-time PSA configuration info
|
| /optee_os/core/lib/qcbor/ |
| H A D | README.md | 230 CMake can also be used to build QCBOR and the test application. Having the root
232 existing CMake environment. The result of the build process is a static library,
233 to build a shared library instead you must add the
240 build).
246 # Configuring the project and generating a native build system
249 cmake --build <build_folder>
255 # Configuring the project and generating a native build system
258 cmake --build <build_folder>
|
| /optee_os/.devcontainer/ |
| H A D | devcontainer.json | 3 "build": { object
|
| H A D | Dockerfile.vscode | 5 build-essential \
|
| /optee_os/.github/ |
| H A D | issue_template.md | 8 the question is about build issues.
|
| /optee_os/core/drivers/crypto/se050/adaptors/utils/ |
| H A D | info.c | 102 LOG_I("%s = 0x%02X", "Tag platform build ID1 (Must be 0x03)", in jcop4_get_id()
104 LOG_I("%s = 0x%02X", "Length platform build ID 0x18", in jcop4_get_id()
106 LOG_MAU8_I("Platform build ID", in jcop4_get_id()
|
| /optee_os/lib/libmbedtls/mbedtls/include/mbedtls/ |
| H A D | build_info.h | 4 * \brief Build-time configuration info
40 /* Macros for build-time platform detection */
|