Experimental Physics and
Industrial Control System

Kay-Uwe Kasemir <[email protected]> · Tue, 30 Oct 2007 09:04:30 -0400

Hi:
For what it's worth, at the SNS we use the C/C++ preprocessor
to process #include and #define statements inside "*.acs" files,
turning them info "*.acf" files.
Below is stuff from the RULES.Db file that I think accomplishes this.
-Kay
#####================ CA security stuff=======================
$(INSTALL_DB)/%.acf: %.acf
        @echo "Installing $@"
        @$(INSTALL) -d -m 644 $(@F) $(@D)
%.acf: ../%.acf
        @$(CP) $< $@
%.acf: %.acs

gcc -E -x c -undef -nostdinc $(ACFLAGS) $(EPICS_DBFLAGS) -o
$@ -c $<

ascheck -S"P=$(IOCNAME)" <$@
$(INSTALL_DB)/%.acs: %.acs
        @echo "Installing $@"
        @$(INSTALL) -d -m 644 $(@F) $(@D)
%.acs: ../%.acs
        @$(CP) $< $@
#=============================================================

On Oct 29, 2007, at 18:58 , Andrew Johnson wrote:
Hi Dayle,
Dayle Kotturi wrote:

Would someone send me an example of the syntax to do this?

There is no support in the language for including other files.
I have an application that has its own access security file
and wants to include packages that have their own .acf files.
If this isn't the right approach, do I just call asSetFilename
multiple times?

The right approach is to have your IOC's build system create a
single file out of the various components. If all you want is
simple include then just cat them all together, but if you need
something more complex you may have to write a script of some kind
(perl, python, shell etc.) to generate the final file that the IOC
will read. The msi tool might also be useful here.
- Andrew
--
When a distinguished but elderly scientist states that something is
possible, he is almost certainly right.  When he states that something
is impossible, he is very probably wrong.  -- Arthur C. Clarke

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System