Move certain "generate" scripts to the framework #91

New issue

Open

opened 2024-12-04 04:37:43 -06:00 by mpg · 0 comments

mpg commented

2024-12-04 04:37:43 -06:00

(Migrated from github.com)

Move the following scripts to the framework:

scripts/generate_features.pl
scripts/generate_psa_constants.py
scripts/generate_query_config.pl
programs/test/generate_cpp_dummy_build.sh (to ./scripts as well)

Note: as of writing, generate_features.pl is identical between 3.6 and development, but the other three have minor differences that need resolving.

For generate_psa_constants.py we probably want to use is_mbedtls_3_6() from the build_tree module. (Once the script is in the framework repo, from . import build_tree should work. From the mbedtls repo, I think we want import framework_scripts_path # pylint: disable=unused-import then from mbedtls_framework import build_tree.)

For generate_cpp_dummy_build.sh we probably want to use in_3_6_branch from scripts/project_detection.sh.

For generate_query_config.pl since this a Perl script we don't have a utility function ready, but I guess a good old-fashioned -d tf-psa-crypto should do nicely.

Move the following scripts to the framework: - [ ] scripts/generate_features.pl - [x] scripts/generate_psa_constants.py - [ ] scripts/generate_query_config.pl - [ ] programs/test/generate_cpp_dummy_build.sh (to ./scripts as well) Note: as of writing, `generate_features.pl` is identical between 3.6 and development, but the other three have minor differences that need resolving. For `generate_psa_constants.py` we probably want to use `is_mbedtls_3_6()` from the `build_tree` module. (Once the script is in the framework repo, `from . import build_tree` should work. From the mbedtls repo, I think we want `import framework_scripts_path # pylint: disable=unused-import` then `from mbedtls_framework import build_tree`.) For `generate_cpp_dummy_build.sh` we probably want to use `in_3_6_branch` from `scripts/project_detection.sh`. For `generate_query_config.pl` since this a Perl script we don't have a utility function ready, but I guess a good old-fashioned `-d tf-psa-crypto` should do nicely.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-Mbed-TLS/mbedtls-framework#91

No description provided.

Rows
Columns