Hi Anton

If it's not possible to avoid a file generation now, it's good to have pre-generated files for a most typical configuration (l2, IPC etc.). As I mentioned before, ideally to use TFM as a real component/framework without generation of any source code.

BUT If you believe, this requirement breaks a TFM concept, just tell us.

Thanks, Andrej

From: TF-M tf-m-bounces@lists.trustedfirmware.org On Behalf Of Anton Komlev via TF-M Sent: Tuesday, October 20, 2020 9:27 AM To: tf-m@lists.trustedfirmware.org Cc: tf-m@lists.trustedfirmware.org Subject: Re: [TF-M] Generated files location

Hi Andrej,

Essentially, do you mean to move the files back to code tree and synch them with templates manually as it was ?

Cheers, Anton

From: Andrej Butok <andrey.butok@nxp.commailto:andrey.butok@nxp.com> Sent: 19 October 2020 16:15 To: Anton Komlev <Anton.Komlev@arm.commailto:Anton.Komlev@arm.com> Cc: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org Subject: RE: Generated files location

Hi Anton,

Another option: 3. Avoid the mandatory on-the-fly generation. Try to make TFM a component/framework, which is configurable by compile & run time parameters.

Thanks, Andrej

From: TF-M <tf-m-bounces@lists.trustedfirmware.orgmailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Monday, October 19, 2020 5:00 PM To: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org Cc: nd <nd@arm.commailto:nd@arm.com> Subject: [TF-M] Generated files location

Hi,

Some source files in TF-M are templated and generated inside /<build_dir>/generated/ on the fly as a part of build process. This guaranty consistency between templates and generated but might make a trouble for IDE, where not all source files exist at the first run. I see 2 options for solution:

1. Explicitly generate those files via cmake as a part of IDE project creation (1 time action) 2. Relay on CMSIS Pack for IDE, where generated files must be presents Any alternative thoughts? Anton