Description
Description of defect
Currently we require an MBED_PATH CMake variable to be defined by the consumer in order for mbed-os to build.
It seems to be poor architecture that we require the application to define this MBED_PATH variable when mbed-os has a hard dependency on it. CMake provides several variables to automatically discover the current path, we should use them if we can. The current system leads to a non-obvious dependency on the consumer. That dependency makes building mbed-os more difficult than it should be in various cases.
If the consumer also needs to include something from mbed-os' CMake modules, e.g to run objcopy in a post build step, they should probably define that path themselves in another variable mbed-os doesn't depend on.
Target(s) affected by this defect ?
all
Toolchain(s) (name and version) displaying this defect ?
all
What version of Mbed-os are you using (tag or sha) ?
mbed-tools 7.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
How is this defect reproduced ?
Just look at files