| 1 |
# RELEASE - Location of external support modules |
| 2 |
# |
| 3 |
# IF YOU CHANGE ANY PATHS in this file or make API changes to |
| 4 |
# any modules it refers to, you should do a "make rebuild" in |
| 5 |
# this application's top level directory. |
| 6 |
# |
| 7 |
# The EPICS build process does not check dependencies against |
| 8 |
# any files from outside the application, so it is safest to |
| 9 |
# rebuild it completely if any modules it depends on change. |
| 10 |
# |
| 11 |
# Host- or target-specific settings can be given in files named |
| 12 |
# RELEASE.$(EPICS_HOST_ARCH).Common |
| 13 |
# RELEASE.Common.$(T_A) |
| 14 |
# RELEASE.$(EPICS_HOST_ARCH).$(T_A) |
| 15 |
# |
| 16 |
# This file is parsed by both GNUmake and an EPICS Perl script, |
| 17 |
# so it may ONLY contain definititions of paths to other support |
| 18 |
# modules, variable definitions that are used in module paths, |
| 19 |
# and include statements that pull in other RELEASE files. |
| 20 |
# Variables may be used before their values have been set. |
| 21 |
# Build variables that are NOT used in paths should be set in |
| 22 |
# the CONFIG_SITE file. |
| 23 |
|
| 24 |
# Variables and paths to dependent modules: |
| 25 |
#MODULES = /path/to/modules |
| 26 |
#MYMODULE = $(MODULES)/my-module |
| 27 |
|
| 28 |
# If building the EPICS modules individually, set these: |
| 29 |
#EPICS_BASE = /path/to/base |
| 30 |
|
| 31 |
# Set RULES here if you want to use build rules from elsewhere: |
| 32 |
#RULES = $(MODULES)/build-rules |
| 33 |
|
| 34 |
# These allow developers to override the RELEASE variable settings |
| 35 |
# without having to modify the configure/RELEASE file itself. |
| 36 |
-include $(TOP)/../RELEASE.local |
| 37 |
-include $(TOP)/../RELEASE.$(EPICS_HOST_ARCH).local |
| 38 |
-include $(TOP)/configure/RELEASE.local |