michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/samples/tfm_integration/tfm_ipc/CMakeLists.txt

14 lines
298 B
CMake
Raw Permalink Normal View History

samples: tfm_integration: Add TFM IPC sample app This commit adds a minimal sample application showing how TF-M can be used in IPC mode, with Zephyr providing the non-secure processing environment image, and linking against the PSA APIs implemented in TF-M. This commit also include work from the commit quoted below, which is included here for attribution purposes: tfm_ipc: cmake: now using tfm_ipc library created by TF-M module This commit removes the need for local knowledge of the TF-M repository structure and files. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> Signed-off-by: Karl Zhang <karl.zhang@linaro.org>
2020-05-08 15:24:02 +02:00
# SPDX-License-Identifier: Apache-2.0
cmake: increase minimal required version to 3.20.0 Move to CMake 3.20.0. At the Toolchain WG it was decided to move to CMake 3.20.0. The main reason for increasing CMake version is better toolchain support. Better toolchain support is added in the following CMake versions: - armclang, CMake 3.15 - Intel oneAPI, CMake 3.20 - IAR, CMake 3.15 and 3.20 Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-08-10 14:44:56 +02:00
cmake_minimum_required(VERSION 3.20.0)
samples: tfm_integration: Add TFM IPC sample app This commit adds a minimal sample application showing how TF-M can be used in IPC mode, with Zephyr providing the non-secure processing environment image, and linking against the PSA APIs implemented in TF-M. This commit also include work from the commit quoted below, which is included here for attribution purposes: tfm_ipc: cmake: now using tfm_ipc library created by TF-M module This commit removes the need for local knowledge of the TF-M repository structure and files. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> Signed-off-by: Karl Zhang <karl.zhang@linaro.org>
2020-05-08 15:24:02 +02:00
samples: make find_package(Zephyr...) REQUIRED This provides a better error message when building with CMake and forgetting ZEPHYR_BASE or not registering Zephyr in the CMake package registry. See parent commit for more details (split from parent for better readability). Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-05-29 06:02:17 +02:00
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
samples: tfm_integration: Add TFM IPC sample app This commit adds a minimal sample application showing how TF-M can be used in IPC mode, with Zephyr providing the non-secure processing environment image, and linking against the PSA APIs implemented in TF-M. This commit also include work from the commit quoted below, which is included here for attribution purposes: tfm_ipc: cmake: now using tfm_ipc library created by TF-M module This commit removes the need for local knowledge of the TF-M repository structure and files. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> Signed-off-by: Karl Zhang <karl.zhang@linaro.org>
2020-05-08 15:24:02 +02:00
project(tfm_ipc)
target_sources(app PRIVATE src/main.c)
modules: tf-m: do not expose TF-M NS interface include directories publicly Instead of exposing publicly the TF-M NS interface include directories, we include them when we build relevant projects. This is required, as the TF-M include directories contains psa crypto sources that are also provided by the mbedtls crypto module. The downside of this solution is that the TF-M includes need to be added explicitly in each application that uses TF-M APIs. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-05-08 23:40:07 +02:00
target_include_directories(app PRIVATE
tf-m: Change NS include path for TF-M 2.0.0 The place where TF-M places its non-secure api header files has changed Therefore changing it for for all applications that use it. Signed-off-by: Markus Swarowsky <markus.swarowsky@nordicsemi.no>
2023-12-08 14:03:30 +01:00
$<TARGET_PROPERTY:tfm,TFM_BINARY_DIR>/api_ns/interface/include
modules: tf-m: do not expose TF-M NS interface include directories publicly Instead of exposing publicly the TF-M NS interface include directories, we include them when we build relevant projects. This is required, as the TF-M include directories contains psa crypto sources that are also provided by the mbedtls crypto module. The downside of this solution is that the TF-M includes need to be added explicitly in each application that uses TF-M APIs. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-05-08 23:40:07 +02:00
)
Copy permalink