CMake: Add support for Mbed TLS Greentea tests

[hugueskamba]

Summary of changes

The Mbed TLS Greentea tests can now be built with CMake.

Building the sanity test requires the following:

1. From the Mbed OS root directory, run cp TESTs/configs/experimental.json /path/to/mbed-os-example-tls/hashing/mbed_app.json
2. From mbed-os-example-tls/hashing, run mbedtools configure -t ARM -m K64F && cp -r .mbedbuild /path/to/mbed-os/connectivity/mbedtls/tests/TESTS/mbedtls/sanity/
3. From mbed-os/connectivity/mbedtls/tests/TESTS/mbedtls/sanity/, run touch mbed-os.lib && mkdir cmake_build && cd cmake_build && cmake .. -G Ninja && cmake --build .

Impact of changes

Migration actions required

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[ciarmcom]

@hugueskamba, thank you for your changes.
@ARMmbed/mbed-os-security @ARMmbed/mbed-os-maintainers please review.

[0xc0170]

Building the sanity test requires the following:

@hugueskamba Is it worth having in docs? readme.md where the tests are ?

[ciarmcom]

This pull request has automatically been marked as stale because it has had no recent activity. @0xc0170, @urutva, @rajkan01, @ARMmbed/mbed-os-maintainers, @ARMmbed/mbed-os-security, please complete review of the changes to move the PR forward. Thank you for your contributions.

[hugueskamba]

Building the sanity test requires the following:

@hugueskamba Is it worth having in docs? readme.md where the tests are ?

This force-push adds information about the need to use specific configuration files when building some Greentea tests.

[0xc0170]

I assume the previous tools also have these json config required to build tests so no change there.

[ciarmcom]

This pull request has automatically been marked as stale because it has had no recent activity. @ARMmbed/mbed-os-maintainers, please start CI to get the PR merged.

[0xc0170]

I'll start CI with other PRs today

[0xc0170]

CI started

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-test	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️