search

bkuner / opcUaUnifiedAutomation

EPICS opcUa device support with Unified Automation C++ based client sdk.
Other
0 stars 4 forks source link

Add mechanism for *.local overrides; .gitignore those files (fixes #8) #15

Closed ralphlange closed 7 years ago

ralphlange commented 7 years ago

Add the necessary includes to the build system files to use *.local overrides for RELEASE and CONFIG_SITE.

ralphlange commented 7 years ago

After applying this commit, you will have to create two *.local files:

CONFIG_SITE.local (probably in OPCUA/configure), setting the SDK location

UASDK = $(TOP)/../../uasdkcppclient-src-debian7.7-x86_64-gcc4.7.2-v1.5.3-346/sdk

RELEASE.local, either in OPCUA/configure (for this TOP) or in OPCUA/.. (for all TOPs below), to set the EPICS location

EPICS_BASE=$(TOP)/../../BASE
bkuner commented 7 years ago

Hi Ralph, the local .local files are a very good idea, but - it seams to me a little overengenered. As I suffer here at BESSY from to much automagic I'd like to keep it simple. Means just local .local files in each TOP.

So I want to reject this pull request and pull a simplified version.

See also the updated README - known bugs!

ralphlange commented 7 years ago

The names and locations have been agreed upon between developers of EPICS Base, areaDetector, and most synApps modules. (Admittedly, synApps is behind in getting the changes into their release.)

What I was proposing is the de-facto standard. Let's please do this as streamlined as possible, and not introduce yet another "simplified" version that introduces confusion and incompatibility, and makes things more complicated in the end.

ralphlange commented 7 years ago

And there's no magic involved. All configuration is kept in human readable files in your local workspace. No external tools or scripts are used or needed.