Experimental Physics and
Industrial Control System

Hi Hinko,

On 08/20/2018 12:06 PM, Hinko Kocevar wrote:
> say I want to install an extra CONFIG file from source configure
> folder to INSTALL_LOCATION/.
> 
> Should I use CFG (INSTALL_LOCATION/cfg) or CONFIGS
> (INSTALL_LOCATION/configure) target in Makefile?
> 
> I would like to include this extra CONFIG in all the dependent
> modules that need this one, in their CONFIG_SITE.

If you want all dependent modules (i.e. other modules that point to this
module in their configure/RELEASE files) to include your file at
build-time, it needs to be in your INSTALL_LOCATION/cfg directory and
have a name starting with "CONFIG" or "RULES" depending on when you want
it to be included by the build system.

Exactly what I need.
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.

 

To achieve this, add the filename to the CFG variable in the Makefile in
the directory where the file is found, and it will be installed for you.

This works as advertised.

Thank you,
Hinko

 

If you want an example, in EPICS 7 the modules/libcom/configure
directory contains these files:

> CONFIG                CONFIG_LIBCOM_VERSION  Makefile  RULES       RULES_TOP
> CONFIG_LIBCOM_MODULE  CONFIG_SITE            RELEASE   RULES_DIRS

The Makefile looks like this:

> #*************************************************************************
> # EPICS BASE is distributed subject to a Software License Agreement found
> # in file LICENSE that is included with this distribution.
> #*************************************************************************
> TOP = ..
> 
> include $(TOP)/configure/CONFIG
> 
> TARGETS = $(CONFIG_TARGETS)
> CONFIGS += $(subst ../,,$(wildcard $(CONFIG_INSTALLS)))
> 
> CFG += CONFIG_LIBCOM_MODULE
> CFG += CONFIG_LIBCOM_VERSION
> 
> include $(TOP)/configure/RULES

The two CONFIG_LIBCOM_* files contain various settings that are needed
later in the build. They get installed into $(INSTALL_LOCATION)/cfg and
are read in as part of the build process for all subsequent parts of the
build. The other EPICS 7 modules have similar files.

These rules for the cfg have been in place since Base-3.14.something,
although the order of inclusions did change in Base-3.15.2 once someone
started to make use of them and suggested improvements.

HTH,

- 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