From 562db1e24cd97b8089fa278e06e14985644f77fb Mon Sep 17 00:00:00 2001 From: Andrew Johnson Date: Mon, 10 Aug 2009 21:15:27 +0000 Subject: [PATCH] Application configure files. --- documentation/RELEASE_NOTES.html | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/documentation/RELEASE_NOTES.html b/documentation/RELEASE_NOTES.html index 1566d3dde..4f8dcfe32 100644 --- a/documentation/RELEASE_NOTES.html +++ b/documentation/RELEASE_NOTES.html @@ -12,6 +12,33 @@

Changes between 3.14.10 and 3.14.11

+

Application configure files

+ +

The configuration directory files installed by makeBaseApp.pl have been +changing in recent releases to make them work more like the files in the Base +configuration directory. The CONFIG_APP file has gone, and its functionality is +now performed by the CONFIG file which should only be modified in exceptional +circumstances. The variables that used to be set in the CONFIG file now appear +in the new CONFIG_SITE file, and can be overridden for specific combinations of +host and target architectures by creating a file with name matching one of these +patterns:

+ + + +

Note that the setting for CHECK_RELEASE in the CONFIG_SITE files is +not compatible with previous releases of Base; if you are creating an +application that has to work with earlier releases, move the +CHECK_RELEASE setting back to the configure/Makefile where it used to +live.

+ +

The RELEASE file(s) can now define the variable RULES if you wish +the application to use build rules from some module other than EPICS_BASE. The +rules must appear in a configure subdirectory just like they do in Base.

+

Compile-time assertions

A new macro has been added to epicsAssert.h which performs assertion checks