TF-PSA-Crypto first all.sh component #40
Labels
No labels
approved
bug
dependencies
DO-NOT-MERGE
enhancement
good-first-issue
help-wanted
historical-reviewed
historical-reviewing
needs-adoption
needs-ci
needs-design-approval
needs-info
needs-preceding-pr
needs-review
needs-reviewer
needs-work
priority-high
priority-low
priority-medium
priority-scheduled
priority-very-high
single-reviewer
size-l
size-m
size-s
size-xs
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-Mbed-TLS/mbedtls-framework#40
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The all.sh script has already been through some changes to be used in the TF-PSA-Crypto repository. It contains
in_(mbedtls|tf_psa_crypto)_repo()functions that are used to execute mbedtls/TF-PSA-Crypto specific shell commands.Depends on all.sh being in the framework, covered by https://github.com/Mbed-TLS/mbedtls/pull/9636.
Following the merge of https://github.com/Mbed-TLS/mbedtls/pull/9445, the all.sh component test_cmake_tf_psa_crypto_out_of_source() has to be moved to a
tf-psa-crypto/tests/components-*.shfile.When executing this component as part of mbedtls CI, the working directory must be
tf-psa-crypto(not the root of mbedtls as it is currently the case in https://github.com/Mbed-TLS/mbedtls/pull/9445) as if all.sh for running that component was called from thetf-psa-cryptodirectory. That way we can remove the change to thetf-psa-cryptodirectory in the component code and the component code and execution are as if we were in the TF-PSA-Crypto directory. To do that we may need to change the CI script calling the components of all.sh?Depends on: https://github.com/Mbed-TLS/mbedtls/pull/9445, https://github.com/Mbed-TLS/mbedtls/pull/9636.
Done in https://github.com/Mbed-TLS/mbedtls/pull/9720.