My 2cts:
IMHO the traditional (more than a decade old) structure for building extensions is deprecated (practically dead).
All current modules and extensions come in the form of standard EPICS software modules.
Such modules can be configured as a set using *.local files in the parent directory of the module set or individually by putting *.local files inside the configure directory of the module.
Cheers,
~Ralph
On 12/7/18 10:26 AM, Torsten Bögershausen via Tech-talk wrote:
> Hej,
>
> Andrew,
> Would it make sense to have a ./configure script in extensions/ ?
> I may be able to provide a patch & pull request some day..