Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Fri, 18 May 2012 15:39:18 -0500

Hi Mark,

On 2012-05-18 Mark Rivers wrote:
> I think we should stick with building one application per detector.  But it
> would be nice to be able to isolate the application (which has lots of
> module dependencies) from the library (which has few dependencies).  It
> seems to me that either means 2 separate configure/RELEASE files, or
> commenting out the extra module lines when only building the library and
> not the application.

You could move the application-specific RELEASE entries into a separate file 
that I'll call the APP-RELEASE file, which the RELEASE file includes; then to 
build only the library the user would just have to comment out the line

    include $(TOP)/configure/APP-RELEASE

from the RELEASE file.

If possible I would recommend that Makefiles should look for defined values of 
their dependent modules to control whether to build their different parts into 
the application (see the usage of SNCSEQ in the makeBaseApp example template), 
but that's not always easy to do so the APP-RELEASE file can also define its 
own variable say BUILD_APP=YES to switch on/off building the application part 
completely.  Then a Makefile could use this technique:

    PROD_IOC_YES = <appname>
    PROD_IOC = $(PROD_IOC_$(BUILD_APP))

With that, <appname> will only be built when BUILD_APP is YES.

HTH,

- Andrew
-- 
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System