Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
7 years ago.
Why does mbed-cli (mbed new) always clone mbed-sdk-tools into every project directory it creates?
Why isn't mbed-sdk-tools just part of mbed-cli, which lives in one place on the user's system? It seems like most of it is scripts that do stuff, not configuration/customization.
1 Answer
7 years ago.
Because this way we can keep evolving the build system with new releases of Mbed OS, without requiring users to update Mbed CLI. Mbed CLI is a front that actually calls the relevant Python script in mbed-os / mbed folder (e.g. build.py does the actual building, and gets invoked by Mbed CLI, but is not part of CLI).
On reading your answer, my first thought was what's the big deal about having to update mbed-cli? But thinking about it a bit more, this way any user necessarily keeps the build tools in sync with the software, so I guess that makes sense.
There would be less duplication if another of my feature ideas were implemented: allow sharing static libraries (esp. mbed-os) among multiple projects #580. :D
posted by 15 Dec 2017