-
Notifications
You must be signed in to change notification settings - Fork 0
integrate tf-psa-crypto 1.x #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: zephyr_tf-psa-crypto_1.0.99_e5fdb3fe2
Are you sure you want to change the base?
Changes from all commits
e37cb7a
ed91dc7
090d5f8
0a428b2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -66,13 +66,13 @@ endif() | |
| set(TF_PSA_CRYPTO_FRAMEWORK_DIR ${CMAKE_CURRENT_SOURCE_DIR}/framework) | ||
|
|
||
| # Put the version numbers into relevant files | ||
| set(version_number_files | ||
| doxygen/input/doc_mainpage.h | ||
| doxygen/tfpsacrypto.doxyfile) | ||
| foreach(file ${version_number_files}) | ||
| configure_file(${file}.in | ||
| ${PROJECT_SOURCE_DIR}/${file}) | ||
| endforeach(file) | ||
| # set(version_number_files | ||
| # doxygen/input/doc_mainpage.h | ||
| # doxygen/tfpsacrypto.doxyfile) | ||
| # foreach(file ${version_number_files}) | ||
| # configure_file(${file}.in | ||
| # ${PROJECT_SOURCE_DIR}/${file}) | ||
| # endforeach(file) | ||
|
Comment on lines
+69
to
+75
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please read: https://docs.zephyrproject.org/latest/develop/modules.html#contributing-changes-to-modules
I'm not sure those changes are acceptable for a Zephyr patch. If this is a problem, I suggest opening a PR upstream trying to make TF-PSA crypto more modular.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I tried to ping Mbed TLS developers on this, but I haven't received any answer so far. I will try to ping them again and if needed I will open a PR upstream to handle this gating this block of code with |
||
|
|
||
| ADD_CUSTOM_TARGET(${TF_PSA_CRYPTO_TARGET_PREFIX}tfpsacrypto-apidoc | ||
| COMMAND doxygen tfpsacrypto.doxyfile | ||
|
|
@@ -396,10 +396,6 @@ if(CMAKE_BUILD_TYPE STREQUAL "Check" AND TEST_CPP) | |
| endif() | ||
| endif() | ||
|
|
||
| if (NOT EXISTS "${TF_PSA_CRYPTO_FRAMEWORK_DIR}/CMakeLists.txt") | ||
| message(FATAL_ERROR "${TF_PSA_CRYPTO_FRAMEWORK_DIR}/CMakeLists.txt not found. Run `git submodule update --init` from the source tree to fetch the submodule contents.") | ||
| endif() | ||
|
|
||
| # | ||
| # Directories with internal headers. The headers in that directories are not | ||
| # exposed to applications and thus not installed. These headers are currently | ||
|
|
@@ -421,7 +417,6 @@ set(TF_PSA_CRYPTO_PRIVATE_INCLUDE_DIRS | |
| # constructed in `drivers/CMakeLists.txt`. This list may include a generated | ||
| # test driver. | ||
| # | ||
| add_subdirectory(framework) | ||
| add_subdirectory(include) | ||
| add_subdirectory(drivers) # must precede core | ||
| add_subdirectory(extras) | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +0,0 @@ | ||
| ###START_GENERATED_FILES### | ||
| /psa_crypto_driver_wrappers.h | ||
| /psa_crypto_driver_wrappers_no_static.c | ||
| /tf_psa_crypto_config_check_before.h | ||
| /tf_psa_crypto_config_check_final.h | ||
| /tf_psa_crypto_config_check_user.h | ||
| ###END_GENERATED_FILES### | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[zep noup]is not an established syntax in Zephyr.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is in the Mbed TLS/TF-M repos: https://github.com/zephyrproject-rtos/mbedtls/blob/zephyr_mbedtls_v3.6.5/README.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, being a submodule of Mbed TLS I followed the same rules specified in that README file.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
already this commit, zephyrproject-rtos/mbedtls@c5b06d8, which changes the README file is violating the established workflow for handling Zephyr modules.
Zephyr module handling and synchronization was thoroughly discussed in the process wg group, as to have a uniform way of dealing with modules in Zephyr.

Do not deviate from that by establishing your own rules.
@tomi-font If you want amendments to the rules, then that should be discussed in the relevant forum first.
A bit of history can be found here:
zephyrproject-rtos/zephyr#27185
https://docs.google.com/presentation/d/1okOQShAr3GZF7VOfRCGa9mw_L7Hyis-oH1kGUpOA66c/edit?userstoinvite=jettrink%40google.com&actionButton=1&slide=id.g81ec62ddd5_0_0#slide=id.g81ec62ddd5_0_0