You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following table lists the files in scripts/.
Necessary for the split (CI+code_size_compare.py): 2M+3S +7XS ~ 5M
In addition to that: 3S
Open questions:
Windows build system?
Do we keep footprint.sh, memory.sh, massif_max.pl and prepare_release.sh?
Table columns legend:
CI: Directly or indirectly necessary to all.sh
F: To be moved to mbedtls-framework (y/n)
C: Used in TF-PSA-Crypto
I: Currently identical between 3.6 and development? (y/n/36/40/-) (36/40 =
present only in that branch, - = no longer present, presumably moved already)
S: Work size for the move and potentially changes needed for TF-PSA-Crypto
CI
F
C
I
S
Issue/PR
Comment
abi_check.py
y
y
y(1.x)
n
S
CI scripts
apidoc_full.sh
y
y
y
y
S
called by doxygen.sh, depends on config.py, needs changes for TF-PSA-Crypto
*.requirements.txt probably should be split differently, with each branch including the framework maintaining requirements for the files that are in that branch. The format supports includes (-r FILENAME, I'm not sure if there are restrictions about directories).
config.pl is for backward compatibility with existing build scripts in 2.x, we should have removed it in 3.x. It's not official but not clearly unofficial either so we should keep it in 3.6 LTS, but it can go away in development.
The following table lists the files in scripts/.
Necessary for the split (CI+code_size_compare.py): 2M+3S +7XS ~ 5M
In addition to that: 3S
Open questions:
Table columns legend:
CI: Directly or indirectly necessary to all.sh
F: To be moved to mbedtls-framework (y/n)
C: Used in TF-PSA-Crypto
I: Currently identical between 3.6 and development? (y/n/36/40/-) (36/40 =
present only in that branch, - = no longer present, presumably moved already)
S: Work size for the move and potentially changes needed for TF-PSA-Crypto
The text was updated successfully, but these errors were encountered: