Add some changes to make the tetramm support module work with builder2ibek.support
recognize that templates in 'all_templates' may be ones that are included by msi directives in other templates. These appear with no substitution list. Skip them and print a message.
treat classes in builder.py with leading underscore as abstract or private and do not try to instantiate them or include them in the support yaml. This is consistent with how builder treats these.
For the tetram there are template subsitutions generated by XML with no indication of the type. The following command overrides a couple of fields that are supposed to be integers:
@JamesOHeaDLS if you try out the above command it should generate you some yaml. Note that the yaml will need a look over manually and there are a couple of TODOs marked in it where the code could not find some of the macros.
I also note that there are some empty 'database' sections which may just need deleting.
You may find it instructive to try without the -o substitutions - you will see that the errors you get make it reasonably clear what sort of overrides are needed.
You should treat this yaml as a first pass to get you started . This tool will never be able to do the full job for any complexity of builder.py. On the other hand the goal for the builder xml -> ioc.yaml is to be perfect and that is the one that will get run many times for every instance of an IOC (it is also fully customizable on a per support module basis).
Add some changes to make the tetramm support module work with builder2ibek.support
For the tetram there are template subsitutions generated by XML with no indication of the type. The following command overrides a couple of fields that are supposed to be integers:
@JamesOHeaDLS if you try out the above command it should generate you some yaml. Note that the yaml will need a look over manually and there are a couple of TODOs marked in it where the code could not find some of the macros. I also note that there are some empty 'database' sections which may just need deleting.
You may find it instructive to try without the -o substitutions - you will see that the errors you get make it reasonably clear what sort of overrides are needed.
You should treat this yaml as a first pass to get you started . This tool will never be able to do the full job for any complexity of builder.py. On the other hand the goal for the builder xml -> ioc.yaml is to be perfect and that is the one that will get run many times for every instance of an IOC (it is also fully customizable on a per support module basis).