Andrew Johnson
31405196cf
Instructions on updating existing modules in the Notes entry. Also prints warning messages from the modules/Makefile if $(INSTALL_LOCATION) is empty.
22 lines
1001 B
Markdown
22 lines
1001 B
Markdown
### Template fix for modules with `cfg/RULES*` files
|
|
|
|
EPICS modules that installed custom build `RULES*` files into
|
|
`$(INSTALL_CFG)` weren't loading them properly when the module
|
|
was built with `INSTALL_LOCATION` set in `configure/CONFIG_SITE`
|
|
or `configure/CONFIG_SITE.local`.
|
|
This release provides a fix in the template `configure/CONFIG`
|
|
file to solve the issue for new modules created from the
|
|
`makeBaseApp` template.
|
|
|
|
Maintainers of old modules that provide special build rules for
|
|
IOC applications should check their `configure` directory.
|
|
Assuming a `configure/CONFIG` file is present, replace it with
|
|
the `templates/makeBaseApp/top/configure/CONFIG` file from this
|
|
release. If any changes were made to the old file they would
|
|
need to be merged into the new file.
|
|
|
|
If the module's `configure` directory contains a file named
|
|
`CONFIG_APP` and no `CONFIG_SITE` file, the application must
|
|
date back to before March 2006; the files in the `configure`
|
|
directory should all be replaced in this case.
|