Google Git
Sign in
pigweed/third_party/github/Mbed-TLS/mbedtls-framework/b6c23e6e0178c96351213d542b6cbae14a3672c2
commit
b6c23e6e0178c96351213d542b6cbae14a3672c2
[log]
author
Gilles Peskine <Gilles.Peskine@arm.com>
Thu Feb 05 13:55:14 2026 +0100
committer
Gilles Peskine <Gilles.Peskine@arm.com>
Thu Feb 05 13:58:22 2026 +0100
tree
ebf7954ad83277c9cd594921613f8a7b1149d584
parent
9dca598383ad1ffb9335d894eef7c270240eeced [diff]
Remove psasim generated files

The files are now generated during the build. Stop having them in version
control.

As formerly in Mbed TLS, `make clean` doesn't remove
configuration-independent target-independent generated files, but the new
target `make neat` does.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
7 files changed
tree: ebf7954ad83277c9cd594921613f8a7b1149d584
  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.