![]() |
![]() ![]()
Experimental Physics and
| ||||||||||||||
|
On 8/10/22 7:35 AM, Yendell, Gary
(DLSLtd, RAL, LSCI) via Tech-talk wrote:
Why should that go into ADCore? You would appear to be adding a dependency which (currently at least) only your site might need. The EPICS build system allows support modules to publish CONFIG_* and RULES_* files that downstream modules (i.e. other modules that point to this module in their configure/RELEASE file) will include automatically, although some aspects of that did change slightly somewhere in the 3.14-3.15 timescale. I would recommend you look into making your changes in a way that downstream IOCs only need to add your module to obtain the additional build functionality. The EPICS State Notation Compiler/Sequencer module does this in its more recent releases, look at its cfg/RULES_SNCSEQ file for one of the earlier examples, and ask here for more details if you do go this route. BTW I know nothing about pvi, we don't use it here so some things in my answer may reflect my ignorance about what it does.
One major change in the build system between 3.14 and 3.15 was that in 3.15 and beyond we expect anyone adding build rules to also provide rules for creating dependency $(DEP) i.e. .d files for their build targets. You might need some conditionals to only enable those dependency rules on 3.15 and later builds, but they are easy to add. I think this is probably causing both problems that you're seeing, you need to provide rules to create your template.d files, and when you do that you can include the yaml file(s) as one of the dependencies, which will then cause later modifications to that file to run the regeneration rules automatically. You can compare the equivalent sections of the Base/configure/RULES_BUILD files for examples of creating the $(DEP) files. HTH, - Andrew -- Complexity comes for free, Simplicity you have to work for.
| ||||||||||||||
ANJ, 14 Sep 2022 |
![]() · Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |