Re: Problem with DB_INSTALLS in Makefile

[Andrew Johnson via Tech-talk <tech-talk at aps.anl.gov>]

Hi Mark,

On 8/31/22 9:40 AM, Mark Rivers via Tech-talk wrote:

I just tested the template file generation in asyn with this command:

/home/epics/devel/asyn/bin/linux-x86_64/makeSupport.pl -t streamSCPI test4

...

This is the Makefile it generated:

**********************

corvette:~/scratch/test4/test4Sup>more Makefile

TOP=..

include $(TOP)/configure/CONFIG

#=======================================

# Install .dbd and .db files

DB_INSTALLS += devtest4.db

DB_INSTALLS += $(TOP)/test4Sup/devtest4.proto

#=======================================

include $(TOP)/configure/RULES

**********************

The Makefile looks OK to me.  I am not sure why the proto file has an explicit path, and the .db file did not, since they are in the same directory.

The makeSupport.pl script is just copying the template files provided by Asyn and substituting macros. makeSupport/streamSCPI/_Name_Sup/Makefile template exactly matches the above. It looks like Janet made a change between Base-3.14.9 and 3.14.10 that modified the DB_INSTALLS rule to do what it does now.

It seems like DB_INSTALLS works if the file has a path, but does not work if the file is in the current directory?

As Michael explained, DB_INSTALLS is now used for installing local copies of files from other modules, whereas DB is used for installing files that come from this source directory. You may be able to use

DB_INSTALLS += ../devtest4.db

instead of DB, but that merely complicates the Makefile.

You'll need to adjust the template files in Asyn as appropriate.

- Andrew

-- 
Complexity comes for free, Simplicity you have to work for.