Fix up some ST CMake targets

[rwalton-arm]

Summary of changes

Some targets weren't factored correctly when the ST target CMake files were changed.
Previously some of the ST targets were implicitly created through various add_subdirectory calls to add the correct source code. So they were missed when we introduced the CMake targets for Mbed targets.

Impact of changes

Migration actions required

Documentation

None

---

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

@Patater @0xc0170

[ciarmcom]

@rwalton-arm, thank you for your changes.
@Patater @0xc0170 @ARMmbed/team-st-mcd @ARMmbed/mbed-os-maintainers please review.

[jeromecoutant]

Tested with 70 targets with STM32.

All OK except FF1705_L151CC

[0xc0170]

I've noticed some of these in #14255 (I can see disco h7 I was just fixing but not correctly, as here
to create base m4/m7 targets).

FF1705_L151CC

This one should be addressed in 14255 , creating a new CMake target that just links to another one.

Can we base this on top of the 14255 ? I would like to get the bigger one in as it blocks couple of PRs.

Pull request has been modified.

[rwalton-arm]

I've noticed some of these in #14255 (I can see disco h7 I was just fixing but not correctly, as here
to create base m4/m7 targets).

FF1705_L151CC

This one should be addressed in 14255 , creating a new CMake target that just links to another one.

Can we base this on top of the 14255 ? I would like to get the bigger one in as it blocks couple of PRs.

I rebased on your branch but the history is now a mess, so I'll wait for your PR to go in before I fix that up.

[jeromecoutant]

Hi
I think you need to rebase
Thx

[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-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-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_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-test	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️