Skip to content
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

Project and branch detection Python and shell utilities #39

Open
1 of 2 tasks
ronald-cron-arm opened this issue Aug 3, 2024 · 0 comments · May be fixed by #67 or Mbed-TLS/mbedtls#9763
Open
1 of 2 tasks

Project and branch detection Python and shell utilities #39

ronald-cron-arm opened this issue Aug 3, 2024 · 0 comments · May be fixed by #67 or Mbed-TLS/mbedtls#9763
Assignees
Labels
enhancement New feature or request size-s Estimated task size: small (~2d)

Comments

@ronald-cron-arm
Copy link
Contributor

ronald-cron-arm commented Aug 3, 2024

When adapting Python and shell scripts to work for mbedtls 3.6, mbedtls 4.0 and/or TF-PSA-Crypto, we often need to detect if the script is called in mbedtls or TF-PSA-Crypto context, if it is called from the root of the project and in the case of mbedtls if the branch is 3.6 or 4.0. The goals of this task are:

  • to complete/improve the Python utility functions in build_tree.py to do the above. Complete: no mbedlts 3.6/4.0 detection for the time being I think. Improve: to distinguish between mbedtls/TF-PSA-Crypto, find a project root, rather use the scripts/project_name.txt file introduced by Standardise Project Detection in Shell Scripts mbedtls#8609 (to be added in tf-psa-crypto/scripts). Done in Projects and Mbed TLS 3.6 detection #45

  • for shell scripts, extend along the lines of what has been done in #8609 to detect between mbedtls 3.6 and 4.0. We should probably create an utility script located in framework/scripts containing the functions in_mbedtls_repo() and in_tf_psa_crypto_repo() as defined in #8609 as well as an is_3_6_branch()/is_4_x_branch() (probably that better names can be found for this functions). The utility script would be "sourced" in test scripts assuming they are called from the root of the repositories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request size-s Estimated task size: small (~2d)
Projects
Status: Framework 1/3 (MVP repo split)
2 participants