RE: Installing extra CONFIG_SITE file

[Hinko Kocevar <Hinko.Kocevar@esss.se>]

 

On 2018-08-21 17:35:18+02:00 Andrew Johnson wrote:

Hi Hinko,

On 08/21/2018 06:43 AM, Hinko Kocevar wrote:
> Silly question: I still need to manually include the CONFIG file I
> installed in the dependent modules CONFIG_SITE, right? As far I see
> there is not automatism here for such custom files like one can find for
> CONFIG, CONFIG_SITE and similar.

No you don't, there is a mechanism in the EPICS build system that

The ultimate solution! That was my goal; avoid dragging the include in all of the dependent modules, but let build system include it automagically..
 

includes those <module>/cfg/CONFIG* files automatically while building
any dependent modules. If you want to know the details, they're in the
Base/configure/CONFIG file, look for RELEASE_CFG_CONFIGS towards the end
of that file. The <module>/cfg/RULES* files are included by the similar
RELEASE_CFG_RULES mechanism in the Base/configure/RULES_FILE_TYPE file.

Works!

Thanks again!

//Hinko
 

The intention was to allow modules to introduce their own rules and
configuration variables without our having to put them in Base. For
example the rules for running the SNC compiler and building sequencer
programs from .st or .stt files could move out of Base into the
sequencer module. This hasn't happened yet, but I hope it will at some
point.

- Andrew

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
</module></module>