Just an FYI;
- Glen: Set up sync meeting to hear Riku/Leonardo/Anton/Joanna on proposing a solution on the git clone performance issue.
Meeting w/ Joanna, Anton, Riku, Leonardo
For TF-M: reviewed proposal(below) by Anton to resolve git check outs. For TF-A: Discussed how this should happen in TF-A This will be tested in stage before pushing to production. *Leonardo will start working on the changes for TF-A immediately.*
If there are any questions, let us know.
Thanks; -g
Anton's proposal:
Let me share my thoughts ahead of the meeting about github download optimisation.
By default TF-M build system downloads all dependent repos for each build to ensure the latest version. Each dependency has a variable, specifying a path to the repo, settled to “DOWNLOAD” by default. “DOWNLOAD” keyword means the build machine has no local copy and the repo shall be cloned. This is documented here:
https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/instru... https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/instructions/tfm_build_instruction.html#manual-dependency-management
I suggest to extend the building process by adding a preliminary CI step of downloading repos once and then specify paths to them for consequent builds via command line parameter, like for example: -DMBEDCRYPTO_PATH=<path for MbedCrypto repo>
Going further, all those build parameters could be gathered in a file and specified for a build using the option TFM_EXTRA_CONFIG_PATH.