Hi Alan,
Currently the generation of these files is a manual step that should be done prior to build.
The script that does the generation is the tools/tfm_parse_manifest_list.py python script. The script has to be run with no command line parameters from the TF-M source root dir. The location of two files, tools\tfm_generated_file_list.yaml and tools\tfm_manifest_list.yaml are hardcoded into the script, and they specify the files the script works on.
tfm_manifest_list.yaml contains the list of partition manifest files. These yaml files provide the information that template files have to be filled with. tfm_generated_file_list.yaml contains the list of files to be generated. The script assumes, that for each <generated_file_path>/<generated_file_name> there is a file <generated_file_path>/<generated_file_name>.template file, which is used as a template for generation.
Please note, that the current version of this script on master contains a custom parser and substituting code, however we have a plan to replace it to the Jinja2 template parser engine. Please see the proposal here: https://developer.trustedfirmware.org/w/tf_m/design/code_generation_with_jin...
Regards, Mate
-----Original Message----- From: TF-M tf-m-bounces@lists.trustedfirmware.org On Behalf Of DeMars, Alan via TF-M Sent: 07 February 2019 22:35 To: tf-m@lists.trustedfirmware.org Subject: [TF-M] generated header files
I'm using the feature-ipc branch and I notice a lot of these warnings in TF-M header files:
/*********** WARNING: This is an auto-generated file. Do not edit! ***********/
When are these files generated? I assume they're derived from associated manifest files.
When I use cmake to create a "ConfigCoreIPC.cmake" build area, I don't see any header files being generated in the process. Any changes I've made to header files with these warnings are still present. Is there a TF-M cmake configuration that regenerates these files? If so, how do I invoke it so I can more properly reconfigure a custom SP?
Alan