Can anyone offer some insight as to how I can go about applying templates from the command-line tool? I’ve been experimenting with it for half-an-hour and I still don’t understand how it’s supposed to work.

I specify the lower-case "-t" option and then give it the path of a template file, followed by the upper-case "-T" to apply, but nothing seems to changing in the compiled events. Furthermore I don’t think I fully understand how this is supposed to work. When I specify a template path, is that an FDT file? Assuming that, how do I specify what template in the FDT to use? There might be a couple dozen. How does the tool know which to use? And beyond that, how can I manage to even create an FDT with just one template in it, if that’s what is required?

[quote="audiodev":cs3csqcz]We use this feature in our build pipeline. When you apply templates (-T) it applies them in memory. It doesn’t modify the fdp. So the fev will have the templates applied even though the fdp doesn’t look any different.[/quote:cs3csqcz]

That part I understand. I guess I should have been more clear and said that I don’t see template changes applied in the FEV at all. And even then, how do I know what template inside the FDT is going to be applied? Is there a way to make a single-template FDT that I’m not aware of?

Every event in the fdt will be applied. Of course, only events that specify a template will be affected. Did you do that part? Each templated event has to explicity say "I use template X".

I’ve been using this feature in our build pipeline for many months now. We’re on 4.19.04 now. I’ll be testing w/ 4.19.06 soon, though I may actually stop using this commandline flag since 4.19.05 added per-project template support.

We use this feature in our build pipeline. When you apply templates (-T) it applies them in memory. It doesn’t modify the fdp. So the fev will have the templates applied even though the fdp doesn’t look any different.