[TF-M] Re: Any usage of environment variables in manifest lists

Hey Kevin

Does this mean that cmake will be required to generate the headers/etc from the manifests?

I believe in the past we deliberately supported the non-cmake usecase, as some people were building TF-M in alternate ways.

Raef

________________________________________ From: Kevin Peng via TF-M tf-m@lists.trustedfirmware.org Sent: 11 May 2022 09:24 To: tf-m@lists.trustedfirmware.org Cc: nd Subject: [TF-M] Any usage of environment variables in manifest lists

Hi,

Is there anyone using environment variables for the “manifest” attribute in out-of-tree manifest lists? I’m asking because I’m working to support configurable stack_size for Secure Partitionshttps://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/15155. In the patch the support of environment variables in manifest lists is removedhttps://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/15155/1/tools/tfm_parse_manifest_list.py#b256. Because I have to call the CMake command configure_file to replace the stack_size symbols (CMake variableshttps://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/15155/1/secure_fw/partitions/crypto/tfm_crypto.yaml#15 surrounded with “@”) with their values. While configure_file does not recognize environment variables.

If you do have environment variables in manifest list, there is an alternative: Replace the env. variables with CMake variables surrounded with “@” and set the value of the CMake variables in either config files or command line inputs.

Best Regards, Kevin