How would a git repo with some submodules preclude any of the things you mentioned? I guess my initial thought is that there would be an “uber” repo in which TFM, CMSIS and mbedcrypto would all be sub-modules.

There’s also the option of using cmake ExternalProject (https://cmake.org/cmake/help/latest/module/ExternalProject.html?highlight=ex...)

Or west

https://pypi.org/project/west/

- k

On Jul 10, 2019, at 8:47 AM, Ashutosh Singh via TF-M tf-m@lists.trustedfirmware.org wrote:

Hi,

Initial idea was to keep the external dependencies clearly visible (from code auditability point of view). With submodule we can't checkout the dependencies out of tree. Since the dependencies need to be checked out only once it was considered acceptable nuisance, until you do a pull and version of the dependencies have changed. 'repo' was considered as well, but repo tool doesn't work on windows(last I checked).

Thanks, Ashu

-----Original Message----- From: TF-M tf-m-bounces@lists.trustedfirmware.org On Behalf Of Kumar Gala via TF-M Sent: 10 July 2019 09:50 To: Andrej Butok andrey.butok@nxp.com Cc: tf-m@lists.trustedfirmware.org Subject: Re: [TF-M] Using git submodules for dependencies?

There can always be a fork of the sources kept in TF-M repos to handle the case of needing local modifications for some reason.

• k

...

On Jul 10, 2019, at 3:48 AM, Andrej Butok via TF-M tf-m@lists.trustedfirmware.org wrote:

Hi Kevin,

Only if 100% of the external project source code is used without change. Even if it is valid now, nobody will give you this guarantee in future.

Regards, Andrej

-----Original Message----- From: TF-M tf-m-bounces@lists.trustedfirmware.org On Behalf Of Kevin Townsend via TF-M Sent: Wednesday, July 10, 2019 10:41 AM To: Thomas Törnblom via TF-M tf-m@lists.trustedfirmware.org Subject: [TF-M] Using git submodules for dependencies?

Hi,

I'm currently working on integrating TF-M into Zephyr and getting TF-M working with QEMU. Part of that work is simplifying the setup and build process to generate a TF-M secure library.

Was the idea of git submodules for dependencies considered and rejected? Using sub-modules would reduce the number of setup steps required, and pair external dependency versions with specific TF-M commits/releases.

There may be a valid reason this approach was rejected, but it seems like a sensible option on the surface?

Best regards, Kevin Townsend -- TF-M mailing list TF-M@lists.trustedfirmware.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.trus... -- TF-M mailing list TF-M@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

-- TF-M mailing list TF-M@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m -- TF-M mailing list TF-M@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m