Add external greentea-client dependency ...

Use FetchContent to obtain greentea-client at version XXX.

CMake: Remove trailing whitespace from CMakeLists.txt

CMake: Remove forgotten debug message ...

A debug message to display the selected toolchain was left in
the main CMakeLists.txt file. This commit removes it.

Merge pull request #14426 from ARMmbed/feature_unittest_refactor ...

CMake: Refactor UNITTESTS CMake

CMake: Move CMAKE_CROSSCOMPILING check inside library CMake

CMake: Only force Ninja response files on Windows ...

We force Ninja to create response files to work around file path length
limitations on Windows. Previously we were forcing the response file
generation for all platforms, unless we were building on Windows using
ARMClang, this was to work around a CMake issue
https://gitlab.kitware.com/cmake/cmake/-/issues/21093

Unfortunately `ar` on macOS doesn't support Ninja response files. So the
check was incorrect, as forcing a response file to be generated on macOS
causes a build failure when trying to build Mbed's unit tests.

This PR changes the logic so we only generate a response file on Windows
systems if we're not building with ARMClang.

Fix missing newline

CMake: Update mbed os, unittest CMake and add CMAKE_CROSSCOMPILING guard ...

- Add a new MbedOS project in mbed os root CMake which can be used along with
  BUILD_TESTING conditional check for enabling the unittest build
- Update UNITTEST CMake for setting the CMake configuration like c, cxx flags etc.,
- Add if CMAKE_CROSSCOMPILING conditional check wherever target configuration check
  and toolchain configuration to avoid such configuration gets included for unittest build.

Cmake: Add backward compatibilty support for MBED_TEST_MODE ...

Fixes #14494

MBED_TEST_MODE is required for backward compatibilty with CLI1. This
adds a test to ensure that the macro is created when using CLI2 for
testing. This also adds a test in `.travis.yml` that checks whether
CMake defines the macro when BUILD_TESTING is on.

CLI1 Reference: https://os.mbed.com/docs/mbed-os/v6.9/debug-test/greentea-for-testing-applications.html

Also, explicitly create and set the macro BUILD_TESTING to allow for
MBED_TEST_MODE to be defined by CMake. MBED_TEST_MODE is required for
backward compatibilty with CLI1.  BUILD_TESTING is used to determine
whether to define MBED_TEST_MODE.  Normally, this would be automatically
done by CTest (which we intend to add for test automation) but this
hasn't yet been added to our Greentea tests.

CMake: set CMAKE_MODULE_PATH in the Mbed OS CMakelists.txt ...

Update CMAKE_MODULE_PATH at once place.

Note, we update also CMAKE_MODULE_PATH in app.cmake. This is temporary until we get a proper way to include
Mbed Os (removing app.cmake need to be included by an application).

CMake: add mbed_ prefix to our CMake files ...

To avoid conflicts as we expose our CMake list files via CMAKE_MODULE_PATH. Some files already include it, this
aligns the rest of files.

I leave app.cmake as it is - it's user facing and it would be breaking change. We can clean this one for the next major version.

CMake tools: use CMAKE_CURRENT_LIST_DIR instead of MBED_PATH ...

Excluding greentea tests, they will be fixed separately (more work needed).

CMake: use project name for Mbed OS ...

This enables multiple variables we can use. One of them is source dir for a project.

It will replace MBED_PATH in the tree.

CMake: Image format based on MBED_OUTPUT_EXT ...

Requires: https://github.com/ARMmbed/mbed-tools/pull/242

The optional `OUTPUT_EXT` field in Mbed OS `targets.json` specifies
the format of the output image. This is important because
* some targets only support one image format
* each post-binary hook outputs one image only

This avoids confusion of having both .hex and .bin images generated
while only one of them is usable.

CMake: pass application name to post-build hook ...

Pass the exact name to the post-build hook, when an application's
or test's `CMakeLists.txt` calls `mbed_set_post_build()`. The
interface is CMake's built-in mechanism:
* `set_target_properties()` to set a property, e.g. application name
* `$<TARGET_PROPERTY:target,property>` to query a property at run time

Force regenerate application binaries on rebuild ...

If a target has a post binary hook, we should force regenerate
the application binaries every time so that the hook is run on a
raw binary rather than a previous build that already went through
the post-build process once.

Configure memory map per target to allow multiple add_executable

Merge pull request #14299 from hugueskamba/hk_cmake_refactor_mapfile_generation ...

CMake: Refactor mapfile generation

Merge pull request #14304 from hugueskamba/hk_cmake_remove_app_target_reference ...

CMake: Refactor post-build hook to remove APP_TARGET references

CMake: Refactor mapfile generation ...

The refactoring was necessary to remove a function call
(mbed_configure_app_target()) from application's CMakeLists.txt.

CMake: Refactor post-build hook to remove APP_TARGET references ...

There should not be a reference to APP_TARGET in Mbed OS as end-users
may decide to use a different name for the CMake variable to store their
application name.

CMake: remove debug print

Merge pull request #14286 from 0xc0170/cmake-fix-remove-target-workaround ...

CMake: remove workaround for targets prior refactor

Merge pull request #14289 from hugueskamba/hk_cmake_refactor_cypress ...

CMake: Refactor Cypress targets

Fix post build mechanism with unique CMake custom targets ...

The CMake custom target must be unique to avoid more than one
Mbed target adding the same. Only the CMake custom command added for the
Mbed target being built is run as the custom CMake target now includes
the Mbed target name.

CMake: remove workaround for targets prior refactor ...

As we refactored all targets, we can remove this workaround from the tree.

CMake: Generate response file before adding mbed-targets ...

We need to generate a "response file" to pass to the C preprocessor
when we preprocess the linker script, because of path length limitations
on Windows. We set the response file and bind the path to a global
property. The MBED_TARGET being built queries this global property when
it sets the linker script.

We must set this global property before the targets subdirectory is
added to the project. This is required because the MBED_TARGET depends
on the response file. If the path to the response file is not defined
when the target requests it the config definitions will not be passed
to CPP.

Merge pull request #14272 from ladislas/ladislas/feature/cmake-current-binary-dir ...

Change CMAKE_BINARY_DIR to CMAKE_CURRENT_BINARY_DIR

Change CMAKE_BINARY_DIR to CMAKE_CURRENT_BINARY_DIR

CMake: Add post build operation support ...

A CMake custom target, mbed-post-build, is added as a dependency of the
application CMake target if a Mbed target adds a CMake custom target
named mbed-post-build-bin. mbed-post-build-bin is added as a dependency
of mbed-post-build. mbed-post-build-bin depends on the application binary.
This is done so a CMake custom command that executes post-build can be added.

The Python scripts that implement the operations have been modified to add
CLI entry points so they can be called from CMake. Dependency on the old
tool has been removed on those scripts by passing them exactly what they
require instead of passing old tool Python objects. A consequence of that
was to slightly amend how the old tool calls some of those Python modules.

Support has only been added for Mbed targets that currently have a requirement
for post build operations. This includes: LPC1114, LPC1768, ARCH_PRO, LPC54114,
LPC546XX, FF_LPC546XX, CY8CKIT064B0S2_4343W, CYTFM_064B0S2_4343W, CYSBSYSKIT_01

The following targets are not supported as TFM support is not yet included:
ARM_MUSCA_B1, ARM_MUSCA_B1_NS, ARM_MUSCA_S1, ARM_MUSCA_S1_NS.