Google Git
Sign in
pigweed/third_party/github/Mbed-TLS/mbedtls-framework/9dca598383ad1ffb9335d894eef7c270240eeced
commit
9dca598383ad1ffb9335d894eef7c270240eeced
[log]
author
Gilles Peskine <Gilles.Peskine@arm.com>
Thu Feb 05 13:49:47 2026 +0100
committer
Gilles Peskine <Gilles.Peskine@arm.com>
Thu Feb 05 13:58:22 2026 +0100
tree
5c7ed34acbc20afc49f0ab38ec66a58f366ecd5e
parent
4b0febffa182d17cb42ccdad14ce414c11641d52 [diff]
Add rules to generate wrappers during the psasim build

We don't need to check those generated files into version control.

This fixes the problem that the generated files have precise knowledge of
the functions that exist on whatever branch of TF-PSA-Crypto is consuming
the framework.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2 files changed
tree: 5c7ed34acbc20afc49f0ab38ec66a58f366ecd5e
  1. .github/
  2. data_files/
  3. docs/
  4. history/
  5. psasim/
  6. scripts/
  7. tests/
  8. .gitignore
  9. CMakeLists.txt
  10. CONTRIBUTING.md
  11. dco.txt
  12. exported.make
  13. LICENSE
  14. README.md
README.md

Mbed TLS framework

This repository contains a version-independent build and test framework for TF-PSA-Crypto and Mbed TLS.

You need this repository as a Git submodule in a branch of one of the above repositories if:

  • You want to build, test or contribute to Mbed TLS 3.6.0 or above, and you are working from a snapshot of a Git commit on a development branch.
  • You want to build, test or contribute to TF-PSA-Crypto, and you are working from a snapshot of a Git commit on a development branch.

You do not need this repository if:

  • You are working with Mbed TLS 2.28.
  • You want to build a release of Mbed TLS and run its unit tests.

Contributing

We gratefully accept bug reports and contributions from the community. Please see the contributing guidelines for details on how to do this.

License

Unless specifically indicated otherwise in a file, Mbed TLS framework files are provided under a dual Apache-2.0 OR GPL-2.0-or-later license. See the LICENSE file for the full text of these licenses, and the ‘License and Copyright’ section in the contributing guidelines for more information.